Acrobat or Adobe Sign transaction limits for individual & business
Complete guide to Transaction limits in Acrobat Pro, Acrobat Standard or Adobe Sign
| Transactions/ User License/ Year | File size/ Upload | Pages/ Transaction | Signers/ Transaction | KBA Transactions | Phone Auth Transactions | |
| Acrobat Standard (except ETLA) | Unlimited (See below) | 10 MB | 100 | 10 | 0 | 0 |
| Acrobat Pro (except ETLA) | Unlimited (See below) | 10 MB | 100 | 25 | 0 | 0 |
| Acrobat Sign SMB (Small Business) & Acrobat Sign for Business (ETLA) | 150 (See below) | 10 MB | 100 | 25 | 0 | 0 |
| Acrobat Sign for Enterprise (ETLA) | 150 (See below) | 10 MB | 500 | 25 | 50/yr | 50/yr |
| Acrobat Sign for Enterprise (VIP) | 150 (See below) | 10 MB | 500 | 25 | 50 | 50 |
Note: For Acrobat Reader users they can send 2 signatures monthy.
Transaction throttling
What is throttling?
All requests made to Acrobat Sign by a client are monitored to protect system resources and preserve our ability to serve as many users as possible.
The rate of resource consumption by the same consumer (e.g., the same userID, IP address, agreement IDs, etc.) is limited (throttled) by the minute, hour, and day.
When a consumer crosses a throttling threshold, that request is rejected with HTTP 429 responses.
What is the allowed rate of requests?
Each request to Acrobat Sign is evaluated based on the amount of system resources it consumes. Different parameters passed to the same endpoint might contribute to a different amount of resource consumption.
Furthermore, some requests may trigger lengthy background processes that are also considered in the throttling evaluation algorithm.
Therefore, the rate of requests can not be described as simple numbers of requests in a certain period of time. Throttling policies are based on historical daily request data, including legitimate usages that stress the system.
Customers can be assured that the Acrobat Sign policies are generous enough that regular daily workflow volume will not be affected.
Note:
Throttling limits apply to each user under an account.
If your system is using utility users to make API calls to Acrobat Sign, it's recommended to distribute the transactions to multiple utility users to reduce the chance of being throttled.
Are all users throttled equally?
No.
Your service package (team, business, enterprise) directly influences your transaction rate.
Higher tiers of service have higher throttle thresholds.
What can I do when my request is blocked?
When a request gets back an HTTP 429 response, it means the user has consumed over the limit of allowed resources in a certain period of time. It could violate the per-minute, -hour, or -day limit.
The error message indicates a number of seconds until the throttling block is lifted and API calls may resume.
REST API calls for agreement creation (including send in bulk, web forms, and templates) or non-REST endpoints return an error like:
- "You've reached the limit on ... at this time. Please try again in <wait_time_in_seconds> seconds."
Requests for any other REST APIs (not agreement creation related) return an error message like:
- "Too many requests. Please try again in <wait_time_in_seconds> seconds."
Requests for any other non-REST endpoints (not agreement creation related) return an error message like:
- "Too Many Requests - The system is busy right now. Come back in <wait_time_in_seconds> seconds."
What if I need to make a legitimate request for a much higher rate than my regular usage?
Paid accounts anticipating a significant event (that may elevate transactional volume above their throttling thresholds) should contact their Success manager to adjust their throttling policy to accommodate their needs.