Argovis API Key Management

In order to allocate our limited resources fairly to all our users, API requests should be accompanied by a free API key that identifies the requester, allowing us to prevent anyone from making so many requests so quickly that they make Argovis unusable for everyone else. Fill out the form below to get yours.

In general, requests made in series (that is, letting your first request finish before issuing the next), should resolve without being cut off by the rate limiter, indefinitely. Making requests in parallel is also possible; exactly how many will be allowed is a function of their estimated size and complexity. Things that reduce estimated request size (and therefore allow you to make more such requests in less time) are:

• Limiting data requests to small geographic and / or short temporal regions
• Requesting only metadata or vocabulary data
• Not including per-level measurements in data requests (ie by omitting the data key)
• Requesting individual data documents by ID
• Requesting small sets of data by groups such as platform or WOCE line as applicable

If you see HTTP 429 errors, you have probably exceeded your request limit with too many concurrent requests! Wait a minute for your allocation to automatically refill, and then try again with less requests in parallel, or by simplifying your requests where possible via the options above.

As always, please reach out to argovis@colorado.edu any time if you need help or have feedback, and we will try to get in touch.