Rate limiting is used to control the amount of traffic sent or received by a network. For example, if you are using an API which is configured to allow 1000 requests per minute, your calls will fail after hitting the limit, typically resulting in a 429 return code. This is a commonly used practice for a better flow of data and to increase security by mitigating attacks such as DoS.
APS APIs have rate limiting as well. When you are writing code for a scalable solution, you will need to take it into consideration, when you hit a limit, you will need to wait until the given period has elapsed and retry. The 429 response will contain a Retry-After HTTP header, which indicates the number of seconds after which the client can call again. Below is an example of a response when hitting a limit:
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 25
Server: Apigee Router
Content-Length: 44
{"developerMessage":"Quota limit exceeded."}
You can find information about rate limiting in Developer Guide section of each API product on the APS developer portal, e.g.,
Requesting a higher rate limit
Rate limit increases are available to ADN members only. If you aren't a member yet, join ADN first, requests from non-members can't be processed.
Before submitting a request, analyze your current usage and propose a limit based on it. Arbitrarily chosen large numbers will not be accepted. The owning product team reviews each request and, if approved, applies the new limit to the specified client ID.
Need to increase the rate limit?
If you would like to increase the rate limit for your application, it is possible by request. Please download and fill out this form “Rate Limit change request form“, and log a ticket though ADN (Autodesk Developer Network) member API support.