Customers should not expect to hit this limit unless they are hitting the API with heavy operations from many concurrent threads at once. To protect our systems and manage availability across customers, we set a reasonable limit on concurrent requests at the account level. ![]() Concurrent Request Limits (Account-Level) Once a rate limit is hit, all further requests will return an error code of 429. We may also lower this limit on a temporary basis to manage API availability. Per Minute Limits (User-Level)Īll API requests will be halted at 900 per user, per minute. This monthly account-level limit resets at the end of each calendar month. Professional tier customers who signed up for Affinity before Jare alotted 40,000 calls per month. Per-minute and concurrent request limits still apply to Enterprise-tier customers. Your account plan tier will limit the overall number of requests you can make per month.Ĭurrent rate limits by plan tier are: Plan Tier We highly recommend designing your application to handle 429 errors. Once a per-minute, monthly, or concurrent rate limit is hit, subsequent requests will return an error code of 429. Requests to both Affinity API versions will count toward the one pool of requests allowed for a user or account. It also sets a reasonable limit on the number of concurrent requests it will support from an account at one time. The Affinity API sets a limit on the number of calls that a user can make per minute, and that all the users on an account can make per month. Requests sent over HTTP will not return any data in order to ensure your sensitive information remains secure. Either a deploy is in process, or Affinity services are down. Service Unavailable - This shouldn't generally happen. Internal Server Error - We had a problem with our server. Too Many Requests - You have exceed the rate limit. In this case, an appropriate error message is delivered. This can also happen in cases the parameters supplied logically cannot complete the request. Unprocessable Entity - Malformed parameters supplied. Not Found - Requested resource does not exist. Here is a list of all the error codes the Affinity API returns in case something does not go as expected: Error Codeįorbidden - Insufficient rights to a resource. Requested, or a valid error message and error code as outlined below. Responses to each request are provided as a JSON object. We provide reading & writing functionality for each NoteĬhanges made through the API will be attributed to the person the API key is assigned to. Otherwise, an error with a code of 401 will be returned. Will need to pass in the key with every API request for us to process it successfully. ![]() You do not need to provide a username.Ĭurrently, we support one key per user on your team. Provide your API key as the basic auth password. Requests are authenticated using HTTP Basic Auth. Support, visit the How to obtain your API Key The Settings Panel that is accessible through the left sidebar on the Affinity web app. To use the API, you will need to generate an API secret key.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |