Adobe Sign API Alternative: Adobe Sign API vs TurboDocx

Adobe Sign API (Acrobat Sign)
Pricing, Rate Limits, SDKs and Webhooks

Adobe publishes no Acrobat Sign API price, bills by transaction, and requires the Business or Enterprise edition for group- and account-level API access. Here is what Adobe documents about developer accounts, embedded signing, SDKs, throttling and webhooks, and how TurboSign compares.

10K+signatures sent
5free signatures a month

Quick answer

Adobe bills Acrobat Sign by transaction, and every agreement sent through the API counts as one against your Business or Enterprise license allowance. Adobe's developer quickstart requires the Business or Enterprise edition for group- and account-level API access, Adobe publishes no API price, and Adobe directs enterprise plan inquiries to its sales team. The free Developer Edition covers testing. Throttled calls return HTTP 429 with a Retry-After value, and identical GET calls are capped at 3 per minute on enterprise and developer tiers. TurboSign includes API access on every tier, 5 free signatures a month, SDKs in 6 languages and webhooks, and is ranked against DocuSign, DocuSeal, SignNow and Dropbox Sign in our eSignature API comparison.

Which Acrobat Sign plan includes API access, and what does it cost?

Adobe's developer quickstart says that granting group-level or account-level OAuth scopes requires the Business or Enterprise edition of Acrobat Sign.

Adobe does not publish an API price. The Acrobat plans and pricing page lists Acrobat Standard, Pro and Studio without any mention of API access, and sends larger organizations to Adobe's sales team for volume licensing. Adobe's Acrobat Sign page presents Acrobat Sign as its standalone e-signature solution for medium and large businesses and routes plan and pricing questions to Contact Sales.

What Adobe does publish is the billing basis. A transaction occurs each time a document, or a set of related documents, is sent to recipients, and an agreement sent from your own app through the Acrobat Sign API is billable the same way as one sent from the web app. Per Adobe's transaction limits page, Acrobat Sign Business and Enterprise plans sold as user licenses include a yearly transaction allowance per user unless your contract says otherwise, and high-volume business and enterprise customers can buy a total volume of transactions with unlimited users through their sales agent. The same page caps Business and Enterprise agreements at 25 signers and 10 MB per uploaded file, with 100 pages per transaction on Business and 500 on Enterprise.

API plans start at $0.30 per signature, with no minimums. Start on the free plan and pay only for the signatures you send beyond it, so a month with one extra signature costs $0.30.

TurboSign includes API access on every tier: Free with 5 signatures a month, Team (currently $10/user/mo) with 15 signatures a month shared across the team, Pro (currently $20/user/mo) with unlimited in-app signing and 60 a month via API key, and Enterprise with custom limits. See TurboSign pricing for current details.

Adobe Sign developer account and API documentation

Adobe offers a free Developer Edition of Acrobat Sign with no commitment. Per the developer guide, it includes access to the Acrobat Sign API plus testing for document exchange, execution and emailing copies of signed agreements, and test documents carry a "test" label. Adobe classes developer accounts as non-billable; if you promote one to a billable plan, existing transactions count as consumed once they are modified.

The Acrobat Sign Sandbox is a different product: a separately entitled, pay-for-access environment that requires an enterprise-level production account with an assigned success manager, and one Sandbox per account.

For the Adobe Sign API documentation itself, Adobe points developers to the REST API v6 reference, the API usage guide on developer.adobe.com and a Postman workspace. Adobe's FAQ notes that support for the legacy SOAP API ended in May 2021.

What are the Adobe Sign API rate limits?

Adobe's API throttling rules limit requests per endpoint at the minute, hour and day levels, applied per user (or per IP address when no user is known), and Adobe says your service plan determines your rate. Throttled calls return HTTP 429 with a THROTTLING_TOO_MANY_REQUESTS code and a Retry-After value in seconds. For accounts created after May 20, 2025, retrying inside that interval throttles the call again and resets the wait. Adobe publishes hard numbers for repeated polling and for webhooks:

Acrobat Sign throttling ruleLimit
REST API requestsPer endpoint, per minute, hour and day; set by your service plan
Identical GET calls (GLOBAL, ENTERPRISE, DEVELOPER tiers)3 per minute
Identical GET calls (all other tiers)3 per 3 minutes
Concurrent webhook creation requests10 per account
Concurrent webhook and callback notifications30 per account
Over the limitHTTP 429 with Retry-After (seconds)

Does the Adobe Sign API support embedded signing?

Adobe documents GET /agreements/{agreementId}/signingUrls, which returns an esignUrl for each signer once the agreement is ready, and describes it for in-person signing on a device. Its developer guide also lists embedding a signing UI in your app. If your product needs to access multiple Acrobat Sign accounts or sign on behalf of other customers, Adobe treats you as an Acrobat Sign Embed partner, a program you join by contacting Adobe.

TurboSign handles embedding through a signing URL your server requests on demand, with per-recipient identity verification. The embedded signing page walks through the flow.

Which SDKs does Adobe offer for Acrobat Sign?

Adobe's SDK downloads page lists C#, Java, JavaScript and OpenAPI SDKs plus REST samples, all in the adobe/acrobat-sign GitHub repository. The same page (last updated January 4, 2024) says the SDKs are obsolete and have not been in sync with the REST v6 API for a while, and points developers to the API endpoints and Postman instead. TurboSign ships official SDKs in 6 languages (TypeScript, Python, PHP, Go, Java, Ruby), all on GitHub, and the code samples below show a full signature request in each.

How do Adobe Sign API webhooks work?

Acrobat Sign webhooks are created through the REST API or the web app, at account, group, user or resource scope (user and resource scope only through the API). Before registering one, Adobe sends a verification request, and your HTTPS endpoint must answer with a 2XX and echo the X-AdobeSign-ClientId value. Adobe's webhook overview says that if your endpoint is down it retries over 72 hours, doubling the interval from 1 minute up to every 12 hours (15 retries); after that, with no successful delivery in 7 days, the webhook is disabled and notifications sent while it is off are lost. TurboSign sends real-time webhook notifications for signature events.

Adobe Sign API vs TurboSign API

The same 7 questions, answered from each vendor's published documentation.

QuestionAdobe Sign API (Acrobat Sign)TurboSign API
Plan needed for API accessAPI FAQ: enterprise and developer tier accounts only. Group and account OAuth scopes need the Business or Enterprise editionAPI access on every tier: Free, Team, Pro and Enterprise. Pro includes 60 signatures a month via API key; API signatures beyond any plan's allowance from $0.30 each (no minimums)
Published API priceNone published. Billed by transaction; Acrobat Sign Business and Enterprise user licenses include a yearly transaction allowance per user unless your contract says otherwiseFree tier with API access; paid plans listed on the pricing page, with a price match guarantee
Free testingFree Developer Edition (test documents carry a "test" label). The Sandbox environment is paid and enterprise-onlyFree plan with 5 signatures a month
Rate limitsPer endpoint per minute, hour and day, set by plan. Identical GET calls: 3 per minute or 3 per 3 minutes by tierCustom API rate limits on Enterprise
Embedded signingGET /agreements/{agreementId}/signingUrls returns an esignUrl per signer; multi-account platforms go through the Embed partner programSigning URL your server requests, with per-recipient identity verification
Official SDKsC#, Java, JavaScript, OpenAPI and REST samples, which Adobe calls obsolete (not in sync with REST v6)6: TypeScript, Python, PHP, Go, Java, Ruby
WebhooksAccount, group, user or resource scope; 15 retries over 72 hours, then the webhook can be disabledReal-time webhook notifications

Comparing more than two vendors? The best eSignature API comparison covers six platforms side by side.

Start Building in Minutes

Choose between our TypeScript SDK for the best developer experience, or use our REST API directly.

send-signature.ts
import { TurboSign } from '@turbodocx/sdk';

// Configure SDK with your credentials
TurboSign.configure({
  apiKey: process.env.TURBODOCX_API_KEY,
  orgId: process.env.TURBODOCX_ORG_ID,
});

// Send for signature using template anchor tags
const result = await TurboSign.sendSignature({
  fileLink: 'https://example.com/contract.pdf',
  documentName: 'Service Agreement',
  recipients: [
    { name: 'John Doe', email: 'john@acme.com', signingOrder: 1 }
  ],
  fields: [
    {
      type: 'signature',
      recipientEmail: 'john@acme.com',
      template: {
        anchor: '{SignHere}',
        placement: 'replace',
        size: { width: 200, height: 50 },
      },
    },
    {
      type: 'date',
      recipientEmail: 'john@acme.com',
      template: {
        anchor: '{DateHere}',
        placement: 'replace',
        size: { width: 150, height: 30 },
      },
    },
  ],
});

// Returns: { success: true, documentId: "...", message: "..." }
// Recipients automatically receive signing invitation via email

Need Python, Go, or other SDKs? Check out our full SDK documentation for all supported languages and frameworks.

Browse All SDKs

Need help integrating? Join our Discord community to get answers from our team and other developers.

Join Discord Community

Adobe Sign API FAQ

Which Adobe Acrobat Sign plan includes API access?

Adobe's developer quickstart says that granting group-level or account-level OAuth scopes requires the Business or Enterprise edition of Acrobat Sign. The Acrobat pricing page (Standard, Pro and Studio plans) does not list API access, and it points larger organizations to Adobe's sales team for volume licensing.

How much does the Adobe Sign API cost?

Adobe does not publish a price for Acrobat Sign API access. Billing is based on transactions: a transaction occurs each time a document (or set of related documents) is sent to recipients, and an agreement sent through the API is billable the same way as one sent from the web app. Acrobat Sign Business and Enterprise plans sold as user licenses include a yearly transaction allowance per user unless your contract says otherwise, and high-volume business and enterprise customers can buy a total volume of transactions with unlimited users through their sales agent.

Is there a free Adobe Sign developer account?

Yes. Adobe offers a free Developer Edition of Acrobat Sign with no commitment. It includes access to the Acrobat Sign API and testing for document exchange, execution and emailing copies of signed agreements, and test documents carry a "test" label. Adobe treats developer accounts as non-billable; if you later promote that account to a billable plan, existing transactions count as consumed once they are modified. The separate Acrobat Sign Sandbox is a paid environment that requires an enterprise-level account with an assigned success manager.

What are the Adobe Sign API rate limits?

Adobe enforces limits per endpoint at the minute, hour and day levels, applied per user (or per IP address when no user is known), and says your service plan determines your rate. Throttled calls return HTTP 429 with a THROTTLING_TOO_MANY_REQUESTS code and a Retry-After value in seconds. Identical GET calls are capped at 3 per minute on GLOBAL, ENTERPRISE and DEVELOPER tiers and 3 per 3 minutes on all other tiers. For accounts created after May 20, 2025, retrying before the Retry-After interval ends resets the wait.

Does the Adobe Sign API support embedded signing?

Adobe documents GET /agreements/{agreementId}/signingUrls, which returns an esignUrl for each signer, and describes it for in-person signing on a device. Its developer guide also lists embedding a signing UI in your app. Platforms whose product needs to access multiple Acrobat Sign accounts fall under the Acrobat Sign Embed partner program, which Adobe asks you to contact it about.

Which SDKs does Adobe offer for Acrobat Sign?

Adobe lists C#, Java, JavaScript and OpenAPI SDKs plus REST samples in its adobe/acrobat-sign GitHub repository, but its SDK page (last updated January 4, 2024) says the SDKs are obsolete and have not been in sync with the REST v6 API for a while. Adobe directs developers to the REST v6 API reference and its Postman workspace instead.

How do Adobe Sign API webhooks work?

You create webhooks through the REST API or the Acrobat Sign web app, at account, group, user or resource scope (user and resource only through the API). Adobe first sends a verification request and your HTTPS endpoint must echo the X-AdobeSign-ClientId value. If your endpoint is down, Adobe retries over 72 hours, doubling the interval from 1 minute up to every 12 hours (15 retries).

How does TurboSign compare to the Adobe Sign API?

TurboSign includes API access on every tier (Free, Team, Pro and Enterprise) and ships official SDKs in 6 languages (TypeScript, Python, PHP, Go, Java, Ruby), real-time webhooks and embedded signing through signing URLs your server requests. The Free plan includes 5 signatures a month, and the Pro plan includes 60 signatures a month via API key, with unlimited in-app signing, and API signatures beyond any plan's included allowance start at $0.30 each with no minimums. Paid plans come with a price match guarantee.

Sources

Adobe Acrobat Sign details checked against Adobe's own documentation in October 2026.

  1. Adobe Help Center: Adobe Acrobat Sign API FAQ
  2. Adobe Help Center: Understand transaction limits
  3. Adobe Help Center: Understand transaction consumption
  4. Adobe Help Center: Acrobat Sign Sandbox overview
  5. Adobe Help Center: Acrobat Sign webhook overview
  6. Adobe Developer: Acrobat Sign developer guide
  7. Adobe Developer: API usage (throttling and signing URLs)
  8. Adobe Developer: Create an application quickstart
  9. Adobe Developer: Acrobat Sign SDK downloads
  10. Adobe Developer: Webhooks in Acrobat Sign
  11. Adobe Developer: Acrobat Sign Embed partner guide
  12. Adobe: Free Developer Edition of Acrobat Sign
  13. Adobe: Acrobat plans and pricing
  14. Adobe: Acrobat Sign for business
  15. Adobe: Acrobat Sign REST API v6 reference
  16. GitHub: adobe/acrobat-sign

Related Resources

Explore more about TurboSign API and developer resources

Ready to Build with TurboSign API?

Start with 5 free signatures a month, API access on every plan, SDKs in 6 languages and real-time webhooks. Paid plans come with a price match guarantee.

5 free signatures/month • API access on every plan • 6 SDKs included