Token request implications
- If you are using the token from the examples on the API Reference page, for extracting information rather than making a request for a token, you run the risk of getting your access to the API blocked. We monitor constantly and will not tolerate abuse.
- We also expect proper use of the API - making too many frequent calls, or too many calls per day might also get your access blocked. We are usually very lenient on the API use, but in some cases we have to maintain steps so that the API is usable by everyone; so if you feel you are a heavy API user, please contact the Red List Unit, as maybe the API is not the best option for you.
- If you need to make frequent calls in one go, please do use at least an appropriate delay between your calls.
- The Red List API is mainly intended for use for helping conservation efforts, be it in the education or research sector. We might not allow access if the API is being used for: mobile app use, part of a computing course, visualisation etc... which is not contributing to what the Red List is about.
- The API data is updated every time there is a new version of the Red List. Therefore, if you are going to be using the Red List data from the API very frequently, it is recommended that you actually store a copy within your systems (please check for permissions first by contacting the Red List), and then update your version whenever there is a new Red List Update.