The Zoo Database API offers developers a streamlined way to access comprehensive information about zoos globally. By tapping into a vast, continuously updated database, this API allows users to retrieve detailed data on zoos by country, continent, and region. It includes information about zoo names, locations, and more.
{"countries":["Belize","Bermuda","Canada","Costa Rica","Guatemala","Mexico","Panama","United States","Argentina","Brazil","Chile","Colombia","Ecuador","French Guiana","Guyana","Paraguay","Peru","Suriname","Uruguay","Venezuela"]}
curl --location --request POST 'https://zylalabs.com/api/6002/zoo+database+api/8043/countries+available+in+dataset' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"continent":"Required"}'
{"zoos":[{"country":"Argentina","zoo_name":"Bubalc\u00f3","location":"General Roca, R\u00edo Negro"},{"country":"Argentina","zoo_name":"Temaik\u00e8n","location":"Bel\u00e9n de Escobar, Buenos Aires Province"},{"country":"Argentina","zoo_name":"Zoo Bat\u00e1n","location":"Mar del Plata, Buenos Aires Province"},{"country":"Argentina","zoo_name":"Zoo C\u00f3rdoba","location":"C\u00f3rdoba, C\u00f3rdoba Province"},{"country":"Argentina","zoo_name":"Zoo de Am\u00e9rica","location":"Rivadavia, Buenos Aires Province"},{"country":"Argentina","zoo_name":"Zoo La Plata","location":"La Plata, Buenos Aires Province"}]}
curl --location --request POST 'https://zylalabs.com/api/6002/zoo+database+api/8044/get+zoos+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Zoo Database API provides access to information about animal species, their habitats, and conservation efforts worldwide. Users can retrieve data on species names, scientific classifications, geographical distribution, habitat types, and conservation statuses.
The API follows the Darwin Core standard for biodiversity data, which ensures compatibility with other biodiversity databases. It utilizes standardized formats such as JSON for data interchange.
The Zoo Database API is built on a RESTful architecture for seamless integration. It requires authentication via API keys to secure access, ensuring that only authorized users can retrieve data.
The output format of the API is structured in a JSON schema that includes nested objects for species details, habitat information, and conservation measures, allowing users to easily retrieve and manipulate the data.
This endpoint returns a list of countries that have zoos listed in the dataset. The response includes an array of country names based on the specified continent parameter.
The response includes an array of zoo objects, each containing fields such as "country," "zoo_name," and "location," providing detailed information about each zoo in the specified country.
Users can customize requests by specifying parameters such as "continent" for the countries endpoint and "country" for the zoos endpoint, allowing targeted data retrieval based on geographic criteria.
The API covers zoos globally, with data organized by continent, including Asia, Africa, the Americas, Europe, and Oceania, allowing users to access information relevant to specific regions.
The response data is structured in JSON format, with clear hierarchies. For example, the zoos endpoint returns an array of zoo objects, each containing nested fields for country, zoo name, and location.
Typical use cases include research on zoo locations, planning visits, educational projects about wildlife conservation, and data analysis for biodiversity studies, leveraging the comprehensive zoo information provided.
Data accuracy is maintained through regular updates and quality checks, ensuring that the information about zoos and their locations is reliable and reflects current conditions.
Users should verify their input parameters for accuracy. If results are still partial or empty, it may indicate that no zoos exist in the specified country or continent, prompting a review of available options.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
1,115ms
Service Level:
100%
Response Time:
4,146ms
Service Level:
100%
Response Time:
5,031ms
Service Level:
100%
Response Time:
406ms
Service Level:
100%
Response Time:
419ms
Service Level:
100%
Response Time:
827ms
Service Level:
100%
Response Time:
458ms
Service Level:
100%
Response Time:
520ms
Service Level:
100%
Response Time:
2,016ms
Service Level:
100%
Response Time:
1,236ms
Service Level:
100%
Response Time:
5,087ms
Service Level:
100%
Response Time:
2,389ms
Service Level:
100%
Response Time:
1,831ms
Service Level:
100%
Response Time:
2,443ms
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
1,604ms
Service Level:
100%
Response Time:
3,309ms
Service Level:
100%
Response Time:
1,935ms
Service Level:
100%
Response Time:
2,155ms
Service Level:
100%
Response Time:
18ms