Last updated on
Sep 1, 2024
Adobe Acrobat Sign transaction limits
Adobe Acrobat Sign limits transactions based on the service level of the sending party per the table below:
|
|
Transactions/ User License/ Year |
File size/ Upload |
Pages/ Transaction |
Signers/ Transaction |
KBA Transactions |
Phone Auth Transactions |
|---|---|---|---|---|---|---|
|
Acrobat Standard |
Unlimited (See below) |
10 MB |
100 |
10 |
0 |
0 |
|
Acrobat Pro |
Unlimited (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign SMB |
150 (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign for Business |
150 (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign for Business |
150 (See below) |
10 MB |
100 |
25 |
50 |
50 |
|
Acrobat Sign for Enterprise |
150 (See below) |
10 MB |
500 |
25 |
50/yr |
50/yr |
|
Acrobat Sign for Enterprise |
150 (See below) |
10 MB |
500 |
25 |
50 |
50 |
Transactions/Acrobat Sign user: A transaction occurs each time an electronic document or collection of related electronic documents is sent to one or more End Users through Acrobat Sign.
Acrobat Sign plans sold as user licenses include 150 transactions per user per year unless otherwise stipulated in your contract.
Business and enterprise-level customers who process a high volume of transactions can speak to their sales agent about buying a total volume of transactions with unlimited users (or a site license).
Refer to the Transaction Consumption article for details on how transactions are consumed.
File size/Upload: Acrobat Sign limits the size of each file uploaded.
If you attempt to upload a document outside this boundary, you get an error under the file that says, "Upload limit exceeded."
Pages/Transaction: The whole transaction (all files merged together) has a total page limit.
If you attempt to send a document that is larger than your account set limit, you get the error "Acrobat Sign was unable to create your agreement because the document(s) exceeded your page limit."
Signers/Electronic transaction: The number of people who can sign an electronic signature transaction varies for each level of service.
Single-user, multi-user for teams, and business service levels have hard caps to the total number of signers their transactions can include.
KBA transactions: Knowledge-Based Authentication (KBA) is an advanced form of signer verification that is enabled at the business and enterprise level of service.
Phone Authentication transactions: Phone Authentication transactions are an advanced form of signer verification that is enabled at the business and enterprise levels of service.
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.
In addition, in rare circumstances, if your use disrupts or risks the system or Adobe’s ability to provide the services, then your use of the product may be turned off temporarily.
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.
No.
Your service package (team, business, enterprise) directly influences your transaction rate.
Higher tiers of service have higher throttle thresholds.
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."
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.