Documenso

DOCS & KNOWLEDGE · TASKS

Envelopes, recipients and signing requests under that person’s own access.

Connecting Documenso in practice

The ceiling is 1,000 requests per minute per IP address, applied globally across /api/v1, /api/v2 and /api/v2-beta together, so every tenant behind one egress address shares it. Buckets are fixed and epoch-aligned, so "the actual wait until the next window is between 1 and 60 seconds" and Retry-After is the only honest guide.

Rate limits

1,000 requests per minute per IP address, applied globally across /api/v1/*, /api/v2/* and /api/v2-beta/*.
Headers: X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (a Unix timestamp for the end of the window).
Free plan: 5 documents per month and 10 total recipients. Paid and Enterprise are unlimited on both.

Worth knowing

The limit is per IP, not per API key, so a shared egress address means one noisy tenant throttles the rest.
"the global API limit uses fixed, epoch-aligned one-minute buckets", so a request arriving at the 59th second gets a one-second wait and one arriving at the first second waits a full minute.
Organizations can configure their own lower limits on top of the global ceiling, so a 429 does not prove 1,000 requests a minute were reached.
The docs warn that "Documents and templates are being deprecated and replaced by envelopes" and point to the OpenAPI reference at openapi.documenso.com because the written guide may lag the endpoints.
Self-hosted instances substitute their own base URL, so none of the figures above describe a customer’s own deployment.

Checked against Documenso public API (2026-09-29), Documenso API rate limits (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

documenso_get_envelopeREAD

Find envelopes based on search criteria via GET /api/v2/envelope

api

documenso_get_envelope_attachmentREAD

Find all attachments for an envelope via GET /api/v2/envelope/attachment

api

documenso_get_envelope_by_envelopeidREAD

Returns an envelope given an ID via GET /api/v2/envelope/{envelopeId}

api

documenso_get_envelope_by_envelopeid_audit_logREAD

Find audit logs based on a search criteria via GET /api/v2/envelope/{envelopeId}/audit-log

api

documenso_get_envelope_by_envelopeid_audit_log_downloadREAD

Download the audit log for a document as a PDF. via GET /api/v2/envelope/{envelopeId}/audit-log/download

api

documenso_get_envelope_by_envelopeid_certificate_downloadREAD

Download the signing certificate for a completed document as a PDF. via GET /api/v2/envelope/{envelopeId}/certificate/download

api

documenso_get_envelope_field_by_fieldidREAD

Returns an envelope field given an ID via GET /api/v2/envelope/field/{fieldId}

api

documenso_get_envelope_item_by_envelopeitemid_downloadREAD

Download an envelope item by its ID via GET /api/v2/envelope/item/{envelopeItemId}/download

api

documenso_get_envelope_recipient_by_recipientidREAD

Returns an envelope recipient given an ID via GET /api/v2/envelope/recipient/{recipientId}

api

documenso_get_folderREAD

Find folders based on a search criteria via GET /api/v2/folder

api

documenso_post_embedding_create_presign_tokenWRITE

Creates a presign token for embedding operations with configurable expiration time via POST /api/v2/embedding/create-presign-token

api

documenso_post_embedding_verify_presign_tokenWRITE

Verifies a presign token for embedding operations and returns the associated API token via POST /api/v2/embedding/verify-presign-token

api

documenso_post_envelope_attachment_createWRITE

Create a new attachment for an envelope via POST /api/v2/envelope/attachment/create

api

documenso_post_envelope_attachment_deleteWRITE

Delete an attachment from an envelope via POST /api/v2/envelope/attachment/delete

api

documenso_post_envelope_attachment_updateWRITE

Update an existing attachment via POST /api/v2/envelope/attachment/update

api

documenso_post_envelope_cancelWRITE

Cancel a pending envelope via POST /api/v2/envelope/cancel

api

documenso_post_envelope_deleteWRITE

Delete an envelope via POST /api/v2/envelope/delete

api

documenso_post_envelope_distributeWRITE

Send the envelope to recipients based on your distribution method via POST /api/v2/envelope/distribute

api

documenso_post_envelope_duplicateWRITE

Duplicate an envelope with all its settings via POST /api/v2/envelope/duplicate

api

documenso_post_envelope_field_create_manyWRITE

Create multiple fields for an envelope via POST /api/v2/envelope/field/create-many

api

documenso_post_envelope_field_deleteWRITE

Delete an envelope field via POST /api/v2/envelope/field/delete

api

documenso_post_envelope_field_update_manyWRITE

Update multiple envelope fields for an envelope via POST /api/v2/envelope/field/update-many

api

documenso_post_envelope_get_manyWRITE

Retrieve multiple envelopes by their IDs via POST /api/v2/envelope/get-many

api

documenso_post_envelope_item_deleteWRITE

Delete an envelope item from an envelope via POST /api/v2/envelope/item/delete

api

documenso_post_envelope_item_update_manyWRITE

Update multiple envelope items for an envelope via POST /api/v2/envelope/item/update-many

api

documenso_post_envelope_recipient_by_recipientid_rejectWRITE

Records a rejection on behalf of a recipient. Use this when a recipient has declined to sign outside of the platform. The rejection is flagged as external in the document audit log. By default the action is attributed to the API user; supply `actAsEmail` to attribute it to a specific team member. via POST /api/v2/envelope/recipient/{recipientId}/reject

api

documenso_post_envelope_recipient_create_manyWRITE

Create multiple recipients for an envelope via POST /api/v2/envelope/recipient/create-many

api

documenso_post_envelope_recipient_deleteWRITE

Delete an envelope recipient via POST /api/v2/envelope/recipient/delete

api

documenso_post_envelope_recipient_update_manyWRITE

Update multiple recipients for an envelope via POST /api/v2/envelope/recipient/update-many

api

documenso_post_envelope_redistributeWRITE

Redistribute the envelope to the provided recipients who have not actioned the envelope. Will use the distribution method set in the envelope. This also refreshes the signing-link expiration for the targeted unsigned recipients, renewing any expired links. via POST /api/v2/envelope/redistribute

api

documenso_post_envelope_updateWRITE

Update envelope properties and settings via POST /api/v2/envelope/update

api

documenso_post_folder_createWRITE

Creates a new folder in your team via POST /api/v2/folder/create

api

documenso_post_folder_deleteWRITE

Deletes an existing folder via POST /api/v2/folder/delete

api

documenso_post_folder_updateWRITE

Updates an existing folder via POST /api/v2/folder/update