Plant Identification API

Machine learning identification of plants and plant diseases from photos

Grow your business with machine-learning plant identification with Plant.id API. It leverages ten years of our domain experience, reaching an outstanding level of proficiency and reliability. We regularly retrain our ML models with better data and state-of-the-art architecture. Over 35,000 plants identified with 93% accuracy.

API Documentation

Endpoints


Send images for identification.



                                                                            
POST https://zylalabs.com/api/4668/plant+identification+api/5889/create+identification
                                                                            
                                                                        

Create Identification - Endpoint Features

Object Description
details [Optional] comma separetad list of requested plant details (optional) : common_names,url,description,taxonomy,rank,gbif_id,inaturalist_id,image,synonyms,edible_parts,watering,propagation_methods
language [Optional] two-letter ISO 639-1 language code (optional, default en) - language of localized plant details can be multiple (up to 3), separated by comma - i.e. (en,de,sv)
async [Optional] boolean (optional) - if true: request does not wait for identification to complete and response does not contain result section; result can be later retrieved by next endpoint
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"Example Response":"No response example available for now."}
                                                                                                                                                                                                                    
                                                                                                    

Create Identification - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/4668/plant+identification+api/5889/create+identification' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "images": ["https://plant.id/static/oak.jpg"],
    "latitude": 49.207,
    "longitude": 16.608,
    "similar_images": true
}'

    

Send images for health assessment. This endpoint is same as "Create Identification" with parameter "health": "only".



                                                                            
POST https://zylalabs.com/api/4668/plant+identification+api/5892/health+assessment
                                                                            
                                                                        

Health Assessment - Endpoint Features

Object Description
language [Optional] two-letter ISO 639-1 language code (optional, default en) - language of localized plant details can be multiple (up to 3), separated by comma - i.e. (en,de,sv)
async [Optional] boolean (optional) - if true: request does not wait for identification to complete and response does not contain result section; result can be later retrieved by next endpoint
full_disease_list [Optional] boolean (optional) - if true: list of suggested diseases contains also general diseases such as "Abiotic"
details [Optional] comma separetad list of requested disease details (optional) see detail description above
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"Example Response":"No response example available for now."}
                                                                                                                                                                                                                    
                                                                                                    

Health Assessment - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/4668/plant+identification+api/5892/health+assessment' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "images": ["https://media.admagazine.com/photos/660a733195c996caa69c1c27/16:9/w_2560%2Cc_limit/calathea-roseopicta-significado.jpg"],
    "latitude": 49.207,
    "longitude": 16.608,
    "similar_images": true
}'

    

Can be used to

  • retrieve identification result when identification is created with async=True
  • retrieve past identifications (available for 6 months)
  • retrieve identification results with different details or languages


                                                                            
GET https://zylalabs.com/api/4668/plant+identification+api/5893/retrieve+identification
                                                                            
                                                                        

Retrieve Identification - Endpoint Features

Object Description
details [Optional] comma separetad list of requested plant details (optional): common_names,url,description,taxonomy,rank,gbif_id,inaturalist_id,image,synonyms,edible_parts,watering,propagation_methods
language [Optional] two-letter ISO 639-1 language code (optional, default en) - language of localized plant details can be multiple (up to 3), separated by comma - i.e. (en,de,sv)
access_token [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"access_token": "bxNJiYHpW5ta1Wh", "model_version": "plant_id:4.0.2", "custom_id": null, "input": {"images": ["https://plant.id/media/imgs/225e36dff19743afad43fa940ab97910.jpg"], "datetime": "2024-07-25T16:51:29.239978+00:00", "latitude": 49.207, "longitude": 16.608, "similar_images": true}, "result": {"is_plant": {"binary": true, "threshold": 0.5, "probability": 0.99858356}, "classification": {"suggestions": [{"id": "f008156f1715de6b", "name": "Quercus petraea", "probability": 0.6258, "similar_images": [{"id": "cab84b41bbba4752ac74fb5fbe157eccf2194b89", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/cab/84b41bbba4752ac74fb5fbe157eccf2194b89.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "Alexander Ordynets", "similarity": 0.818, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/cab/84b41bbba4752ac74fb5fbe157eccf2194b89.small.jpeg"}, {"id": "96ca4ded93fc67d5f56e21e0140feced370fd3a5", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/96c/a4ded93fc67d5f56e21e0140feced370fd3a5.jpeg", "license_name": "CC BY-SA 4.0", "license_url": "https://creativecommons.org/licenses/by-sa/4.0/", "citation": "Sylvain Gaudin", "similarity": 0.735, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/96c/a4ded93fc67d5f56e21e0140feced370fd3a5.small.jpeg"}], "details": {"language": "en", "entity_id": "f008156f1715de6b"}}, {"id": "a6b75b7696d0c2f4", "name": "Quercus cerris", "probability": 0.1659, "similar_images": [{"id": "e56e951983b049fb6ed1fe0c74effcf381e4d176", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/e56/e951983b049fb6ed1fe0c74effcf381e4d176.jpeg", "license_name": "CC BY-SA 4.0", "license_url": "https://creativecommons.org/licenses/by-sa/4.0/", "citation": "Lugifa Lugifa", "similarity": 0.775, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/e56/e951983b049fb6ed1fe0c74effcf381e4d176.small.jpeg"}, {"id": "a9ecb27835b221c8d7243f464e8ca613afd57831", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a9e/cb27835b221c8d7243f464e8ca613afd57831.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "Kai Best", "similarity": 0.769, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a9e/cb27835b221c8d7243f464e8ca613afd57831.small.jpeg"}], "details": {"language": "en", "entity_id": "a6b75b7696d0c2f4"}}, {"id": "968d8d141ab1ce44", "name": "Quercus robur", "probability": 0.1185, "similar_images": [{"id": "fe578bfed73d90a29f9f780b55a4751ca29aeeab", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/fe5/78bfed73d90a29f9f780b55a4751ca29aeeab.jpeg", "license_name": "CC BY-NC-SA 4.0", "license_url": "https://creativecommons.org/licenses/by-nc-sa/4.0/", "citation": "FlowerChecker s.r.o.", "similarity": 0.906, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/fe5/78bfed73d90a29f9f780b55a4751ca29aeeab.small.jpeg"}, {"id": "b97c7f56a0d5b760194bc4fd71c444f404f8aaeb", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/b97/c7f56a0d5b760194bc4fd71c444f404f8aaeb.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "Ewa Julia Kuerten", "similarity": 0.754, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/b97/c7f56a0d5b760194bc4fd71c444f404f8aaeb.small.jpeg"}], "details": {"language": "en", "entity_id": "968d8d141ab1ce44"}}, {"id": "8021a9c6893677b7", "name": "Quercus pubescens", "probability": 0.0474, "similar_images": [{"id": "a96fb3b61462c7bda2ed3caf40c3953a73282a69", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a96/fb3b61462c7bda2ed3caf40c3953a73282a69.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "Danilo D'Auria", "similarity": 0.895, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a96/fb3b61462c7bda2ed3caf40c3953a73282a69.small.jpeg"}, {"id": "8b99a6e1d635e1b28b4893df82f5daa1898cf851", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/8b9/9a6e1d635e1b28b4893df82f5daa1898cf851.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "dawk stah", "similarity": 0.759, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/8b9/9a6e1d635e1b28b4893df82f5daa1898cf851.small.jpeg"}], "details": {"language": "en", "entity_id": "8021a9c6893677b7"}}, {"id": "ad0c114cd51d3c2e", "name": "Quercus pyrenaica", "probability": 0.0108, "similar_images": [{"id": "c0722366dbe7136686bbfdd21f9810507f08cc83", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/c07/22366dbe7136686bbfdd21f9810507f08cc83.jpeg", "license_name": "CC BY-SA 4.0", "license_url": "https://creativecommons.org/licenses/by-sa/4.0/", "citation": "Tela Botanica \u2212 Florent BECK", "similarity": 0.89, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/c07/22366dbe7136686bbfdd21f9810507f08cc83.small.jpeg"}, {"id": "a8d1f8c4746404d4cfcb00dbc8e953bc3890f15f", "url": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a8d/1f8c4746404d4cfcb00dbc8e953bc3890f15f.jpeg", "license_name": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "citation": "Pablo Amieiro", "similarity": 0.746, "url_small": "https://plant-id.ams3.cdn.digitaloceanspaces.com/similar_images/4/a8d/1f8c4746404d4cfcb00dbc8e953bc3890f15f.small.jpeg"}], "details": {"language": "en", "entity_id": "ad0c114cd51d3c2e"}}]}}, "status": "COMPLETED", "sla_compliant_client": true, "sla_compliant_system": true, "created": 1721926289.239978, "completed": 1721926289.792683}
                                                                                                                                                                                                                    
                                                                                                    

Retrieve Identification - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4668/plant+identification+api/5893/retrieve+identification&access_token=Required' --header 'Authorization: Bearer YOUR_API_KEY' 

    

This endpoint will allow you to delete any identifications based on its access_token



                                                                            
DELETE https://zylalabs.com/api/4668/plant+identification+api/5894/delete+identification
                                                                            
                                                                        

Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"Example Response":"No response example available for now."}
                                                                                                                                                                                                                    
                                                                                                    

Delete identification - CODE SNIPPETS


curl --location --request DELETE 'https://zylalabs.com/api/4668/plant+identification+api/5894/delete+identification&access_token=Required' --header 'Authorization: Bearer YOUR_API_KEY' 

    

Can be used to send a user feedback to an identification.

Specifics:

  • data must be in the form of JSON
  • recommended structure is either rating - a number from 0-5 or comment - a text comment from the user. Or include both
  • We will attach feedback to identification and it will be returned in next retrieve of identification.

Feedback can help us improve our model, so thank you for sending it.



                                                                            
POST https://zylalabs.com/api/4668/plant+identification+api/5896/send+feedback
                                                                            
                                                                        

Send Feedback - Endpoint Features

Object Description
Request Body [Required] Json
access_token [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            Feedback submitted successfully.
                                                                                                                                                                                                                    
                                                                                                    

Send Feedback - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/4668/plant+identification+api/5896/send+feedback&access_token=Required' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "rating": 5,
    "comment": "Identified poisonous plant, saved my cat! Thanks."
}'

    

This endpoint is alpha beta testing and can change!

Search plant knowledge base by query. Plants are searchable by scientific names, common names (in specified language), synonyms.

Plant name and query are always matched from start of a word., i.e. "Aloe vera" is searchable by "Aloe", "Alo", "Vera", "ver", "Aloe vera"..



                                                                            
GET https://zylalabs.com/api/4668/plant+identification+api/5897/plants+search
                                                                            
                                                                        

Plants search - Endpoint Features

Object Description
thumbnails [Optional] bool (optional) - add for each result 64x64 thumbnail encoded as base64 image
q [Required] Search query
limit [Optional] int (optional) - maximum of returned result, max. 20, default 10
lang [Optional] two-letter ISO 639-1 language code (optional, default en) - language of common names can be multiple (up to 3), separated by comma - i.e. (en,de,sv)
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"entities": [{"matched_in": "Aloe vera", "matched_in_type": "entity_name", "access_token": "XGhTMStKZFRgVQNlaVgCMntOalpzR3pCYlNbbFZlAzI-", "match_position": 0, "match_length": 9, "entity_name": "Aloe vera"}, {"matched_in": "Aloe vera", "matched_in_type": "synonym", "access_token": "CmgIMX5KNlRhVQFlYFgEMixOOFpzR3RCY1MKbFdlCjI-", "match_position": 0, "match_length": 9, "entity_name": "Aloe succotrina"}, {"matched_in": "Aloe vera var. officinalis", "matched_in_type": "synonym", "access_token": "C2hXMSlKbVRtVVJlYFhUMipOaFojRydCYlNcbFNlBTI-", "match_position": 0, "match_length": 9, "entity_name": "Aloe officinalis"}], "entities_trimmed": false, "limit": 10}
                                                                                                                                                                                                                    
                                                                                                    

Plants search - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4668/plant+identification+api/5897/plants+search?q=aloe vera' --header 'Authorization: Bearer YOUR_API_KEY' 

    

This endpoint allows you to ask the LLM chatbot questions about an identification. Every other call adds another question and the bot's answer to conversation.

Parameters in POST JSON data:

  • question - string - user's question to chatbot

  • prompt - string - optional, allowed only for first question - extra text added to initial prompt that can modify chatbot's behaviour during conversation

  • temperature - float - optional, allowed only for first question - ranges 0-2; default is 0.5; lower temperature gives more deterministic output, higher values give more random output

  • app_name - string - optional, allowed only for first question - chatbot uses this identity if asked about itself



                                                                            
POST https://zylalabs.com/api/4668/plant+identification+api/5899/ask+chatbot
                                                                            
                                                                        

Ask chatbot - Endpoint Features

Object Description
Request Body [Required] Json
access_token [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"messages": [{"content": "Is this plant edible?", "type": "question", "created": "2024-07-25T17:09:13.250Z"}, {"content": "The plant suggested is QUERCUS PETRAEA, also known as Sessile Oak. OAKS, INCLUDING SESSILE OAKS, ARE NOT COMMONLY CONSIDERED EDIBLE FOR HUMANS DUE TO HIGH TANNIN CONTENT IN THEIR ACORNS. IT IS NOT RECOMMENDED TO EAT PARTS OF THIS PLANT.", "type": "answer", "created": "2024-07-25T17:09:13.250Z"}, {"content": "Is this plant edible?", "type": "question", "created": "2024-07-25T17:09:25.107Z"}, {"content": "The plant suggested is QUERCUS CERRIS, also known as European Turkey Oak. OAKS, INCLUDING EUROPEAN TURKEY OAKS, ARE NOT COMMONLY CONSIDERED EDIBLE FOR HUMANS DUE TO HIGH TANNIN CONTENT IN THEIR ACORNS. IT IS NOT RECOMMENDED TO EAT PARTS OF THIS PLANT.", "type": "answer", "created": "2024-07-25T17:09:25.107Z"}, {"content": "Is this plant edible?", "type": "question", "created": "2024-07-25T17:12:00.460Z"}, {"content": "The plant suggested is QUERCUS ROBUR, also known as English Oak or Pedunculate Oak. OAKS, INCLUDING ENGLISH OAKS, ARE NOT COMMONLY CONSIDERED EDIBLE FOR HUMANS DUE TO HIGH TANNIN CONTENT IN THEIR ACORNS. IT IS NOT RECOMMENDED TO EAT PARTS OF THIS PLANT.", "type": "answer", "created": "2024-07-25T17:12:00.460Z"}], "identification": "wdLeOuU79IxeSTj", "remaining_calls": 17, "model_parameters": {"model": "gpt-3.5-turbo", "temperature": 0.5}, "feedback": {}}
                                                                                                                                                                                                                    
                                                                                                    

Ask chatbot - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/4668/plant+identification+api/5899/ask+chatbot&access_token=Required' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "question": "Is this plant edible?",
    "prompt": "Give answer all CAPS.",
    "temperature": 0.5,
    "app_name": "MyApp"
}'

    

Can be used to send user feedback to a chatbot conversation.

Specifics:

  • data must be in the form of JSON under feedback field

  • recommended structure is either rating - a number in the range 0-5 or comment - a text input from the user. Both can be included.

Feedback can help us improve our model.



                                                                            
POST https://zylalabs.com/api/4668/plant+identification+api/5900/send+feedback+on+chatbot+conversation
                                                                            
                                                                        

Send feedback on chatbot conversation - Endpoint Features

Object Description
Request Body [Required] Json
access_token [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status": "ok"}
                                                                                                                                                                                                                    
                                                                                                    

Send feedback on chatbot conversation - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/4668/plant+identification+api/5900/send+feedback+on+chatbot+conversation&access_token=Required' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "feedback": {
        "rating": 5,
        "comment": "Very usefull"
    }
}'

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Plant Identification API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

The plant identification process currently involves three independent models: Genus model (such as Philodendron) Species model (such as Philodendron hederaceum) Infraspecies model (such as Philodendron hederaceum var. oxycardium β€˜Brasil’) You can choose which model’s results are shown in the response by using the classification_level parameter.Results from each model are post-processed in several steps where classes may be merged and probabilities adjusted. It involves re-evaluating the response to avoid duplicate information. If you want to omit the postprocessing and get the original response instead, you can set classification_raw=true. See the example.

We can currently identify around 30,000 plant species of various life forms. You can explore how our model performs on houseplants, garden ornamentals, trees and shrubs, weeds, European or American wild plants.

See available plant details in the API response in the documentation. The following table shows the content coverage for classes in the Plant.id database. Content coverage: url 100% Taxonomy – Kingdom 100% Taxonomy – Phylum 100% Taxonomy – Class 100% Taxonomy – Order 100% Taxonomy – Family 100% Taxonomy – Genus 100% GBIF id 99.99% iNaturalist_id 98.65% Wikipedia image 99.12% Propagation methods 9.16% Edible parts 8.80% Watering 9.50%

Yes, we can! Our latest model update from October 2023 (read a blog post for more) includes a capability to identify so-called infraspecific taxa, which include plant varieties, cultivars and subspecies. However, this is not a default setting of the API; in the Identification request, you need to set the classification_level = all. See the example.

Yes, we have an extra model is_healthy that can identify whether a plant is healthy or diseased. You can use the health = auto attribute to decide whether an image should undergo a Health Assessment automatically. If the model’s output exceeds a specific threshold, indicating the presence of a diseased plant, the image will be sent to the Health Assessment. If the plant is considered healthy, the cost is one credit. If the plant is considered diseased and a Health Assessment is requested, the cost is two credits. If you want responses from both Species Identification and Health Assessment, you can set the parameter health = all. The total cost would be two credits.

The cost is one identification credit, the same as for plant identification. In case you want both the Species Identification and Health Assessment results for a single plant, the cost is one credit for each product.

Diagnosing plant health is often a complex task. For example, if a plant is consistently overwatered, it is also unable to use nutrients effectively, so it will develop symptoms of both overwatering and nutrient deficiency. Therefore, when implementing this functionality, we recommend that you list more than one possible cause of disease in the result. However, you can also improve the result by taking a photo of a diseased part of a plant for best results. Some diseases have less visible symptoms (e.g. small pests), and the detail is crucial for correct identification.

With Plant disease identification API you can recognize: 28 classes of fungal diseases 18 classes of abiotic disorders 17 classes of pests 7 classes of chromista 5 classes of viruses 5 classes of bacterial diseases The full list of diseases changes dynamically. If there is a reason you need the full list, please let us know at [email protected].

You can use the redundant attribute for discarding parent classes. Discarding parent classes is useful when the difference between the probability of the parent class (higher in the hierarchy) and the child class (lower in the hierarchy) is insignificant. In this case, classes that can be discarded have a boolean attribute redundant in the response.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.


Related APIs