Rate limiting is used to control amount of traffic sent or received by a network. For example, if you are using a certain API which is configured to allow 1000 requests per minute, your call will fail after hitting the limit, typically resulting 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 API has rate limiting as well. When you are writing a code for scalable solution, you will need to take it into consideration; i.e., When you hit a limit, you will need to wait till given period has lapsed and retry. 429 response will contain “Retry-After” http header, which indicates the number of seconds after which the client can call again. Below is an example of 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.,
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.
Before you request, please make sure to analyze the current usage and provide a reasonable value. Arbitrary chosen large numbers are not accepted. Upon request, each product team will evaluate and if accepted, higher rate limit will be set to the given client id.
