DocuSign API Pricing: DocuSign API Cost, eSignature REST API Plans and Envelope Limits

These are DocuSign's self-serve developer plans, read from its plans and pricing page for developers on August 20, 2026 and shown in US dollars. All three carry a note that additional tax may apply, so treat these as pre-tax figures.

Starter is flagged as the most popular tier on DocuSign's page. Enhanced is the only one without a published price, and DocuSign lists a sales number rather than a checkout button for it.

One correction worth making plainly, because it is repeated in nearly every competing article on this topic: DocuSign API pricing is not $75, $450 and $720. That was an older schedule. The current published prices are $50, $300 and $480, and if you are building a cost model you should use those.

Between $1.25 and $4.80 per envelope on the developer plans, if you use the whole allowance. Divide the annual price by the annual envelope allowance and the plans separate sharply. Starter is the cheapest per envelope DocuSign publishes anywhere, including its web plans, and Advanced is the most expensive.

The developer plan figures come from DocuSign's page on August 20, 2026. The three web plan rows use DocuSign's published US list prices of $11, $30 and $45 per user per month, last checked in July 2026, against the allowances DocuSign documents for those tiers. We have kept them in the same table because the comparison is the point, but the sourcing is not identical and you should treat the API rows as the firmer numbers.

Two things fall out of that table. The first is that API Starter, at $1.25 an envelope, is better value per send than any web plan DocuSign sells, which is not what most people expect from a developer tier. The second is that Advanced costs $4.80 an envelope for exactly the same volume Intermediate gives you at $3.00. The extra $1.80 is a feature charge wearing a volume charge's clothes.

Yes. DocuSign publishes an eSignature REST API along with software development kits for the common languages, mobile SDKs, an API usage center and an API dashboard. Authentication is OAuth 2.0, and DocuSign requires it for any integration going to production. There are additional APIs beyond eSignature for notary, ID Evidence and other capabilities.

The API is genuinely good, which is a large part of why DocuSign is embedded in so much other software. The friction is not technical. It is that access to it is priced and metered separately from the subscription most companies already have, and that catches people out at exactly the wrong moment, usually the week they planned to launch.

Partly. DocuSign gives you a free developer account with no time limit, and you can build and test against the full API in its demo environment. What you cannot do is use it for real business. Envelopes sent from a demo account are not legally binding, and they carry demo watermarking. To send anything that counts, you have to complete DocuSign's go-live process and move the integration to a paid production account.

DocuSign is explicit about this in its production requirements: going live requires OAuth 2.0 configured for the application, administrator access to the target production account, and a paid production account to manage the integration. The one carve out is that ISV partners may qualify for a free management account through the partner program.

Demo accounts also have their own allowance, which is why developers regularly hit an envelope allowance error while load testing. That is a demo cap, not a billing problem, and it does not predict what your production plan will allow.

Usually not, and this is the single most expensive misunderstanding in DocuSign pricing. DocuSign counts sending as two separate things. A person logging in and sending from the web app spends a web application envelope. Your code or an integration sending the same agreement spends an automation send. They draw on different allowances, and on a user-based eSignature plan the automation allowance is listed as not included at all.

Read the unlimited rows carefully. An IAM Professional account can send as many envelopes as it likes through the browser and is still capped at 100 API sends per user per year. That is roughly two a week. A modest integration will burn through it in a month, and the error you get says the envelope allowance for the account has been exceeded while the billing screen still says unlimited.

DocuSign has changed these allowances several times and dates each change by order start date. Subscriptions starting on or after August 28, 2024 saw automation sends rise from 50 to 100 per user per year on IAM Standard, Professional, Enterprise, for Sales and for CX. Subscriptions starting on or after November 21, 2025 have that 100 per user per year allowance pooled at the account level rather than held per seat, which helps uneven teams. Subscriptions starting on or after February 20, 2026 on IAM Enterprise, for Sales and for CX get a separate allowance of 200 third party integration sends per user per year, also pooled at the account level. Your start date decides which of these you get.

One caveat on sourcing. DocuSign publishes that allowance table for customers who bought a subscription through a DocuSign sales representative or partner, and points customers who bought on the website to the plans and pricing page instead. If you bought online, confirm your own numbers in Plan and Billing before you commit to an architecture.

Basic API was the entry level name DocuSign used for its developer tier in an earlier lineup, alongside Intermediate and Advanced. It still shows up in search, in old forum threads and in a lot of third party write-ups. The current self-serve lineup on DocuSign's developer plans page is Starter, Intermediate, Advanced and Enhanced.

If you are searching for how to upgrade a Basic API plan, what you are looking for now is Starter. The practical answer is the same either way: upgrading changes both the envelope allowance and the feature set, and bulk send through the REST API only appears at Advanced.

Open a free developer account, build against the demo environment, then submit the integration through the go-live process and promote it to a paid production account. DocuSign has moved go-live into the Developer Console, where you can take an integration live from the console once it passes review. The promotion copies your integration key into production rather than moving it, so your demo integration keeps working, but secrets and redirect URIs are not copied and have to be configured again on the production side.

Every integration, whatever API it uses, has to have account access to each API it calls, stay inside the published API resource limits, use OAuth 2.0 authentication, and declare the correct integration classification. That last one is not cosmetic. It determines both the review path and how you are billed in production.

Once submitted, your app shows one of four review statuses. The two worth planning around are Review Expired and Declined, because both cost you calendar time you probably budgeted for launch.

The ninety day expiry is the trap. Teams pass review early, the launch slips a quarter, and the review has to be run again. If your ship date is uncertain, submit closer to it rather than earlier.

Separate from what you pay for, DocuSign enforces platform limits on every account. These are the ones that shape how you build, and they apply whichever developer plan you are on.

The polling rule is the one that surprises new integrations. DocuSign expects you to use Connect webhooks for status rather than polling, and polling an envelope more often than every fifteen minutes is outside its published guidance. Build around webhooks from the start and you avoid a rewrite later.

A fair number of the teams pricing an API plan do not need one. It is worth being honest about which camp you are in before you commit to $3,600 or $5,760 a year, because the answer is often no.

You probably do need the API if you are embedding signing inside your own product, if signature requests have to fire from an event in your system with no human involved, if you need signed documents written back into your database automatically, or if you are shipping this to your own customers.

You probably do not need it if the real requirement is sending the same document to a lot of people, which is bulk send rather than an integration, or if what you want is to stop paying per envelope. In that second case an API plan makes the problem worse: it introduces a second meter alongside the one you already have. Plenty of teams reach for an integration when what they actually wanted was a flat bill and a browser tab.

SignSend is built for that second group, and we are not going to pretend otherwise. There is no SignSend API today. What there is: upload a PDF, add your signers, send it, and the signed file comes back with an audit trail, for $12 a month with unlimited documents and no envelope counter. If your sending is done by people rather than code, that is usually the cheaper answer by a wide margin.