All integrations

eSignatures.com

DOCS & KNOWLEDGE · FILES & DOCS

Contracts out for signature, their signers, templates, and PDFs in the account they connected.

Connecting eSignatures.com in practice

eSignatures.com has no API-key header: the secret token is the HTTP Basic username with an empty password, or a `?token=` query parameter, which is how a signing credential ends up in proxy logs. Rate limiting is "adaptive" rather than a published figure, and the docs explicitly tell you not to poll GET /api/contracts/<id> — contract status is meant to arrive by webhook.

Scopes that draw scrutiny

  • Secret Token (eSignatures.com’s own term) One token, no scopes, sent as the Basic auth username or in the query string. It can create legally binding contracts and read every signed PDF in the account.
  • test: "yes" Not a credential but the only thing separating a rehearsal from a real send: the same token creates demo and live contracts, and the flag is per request.

Rate limits

  • Adaptive rate limiting that adjusts to your usage pattern; no fixed requests-per-second figure is published.
  • The documentation explicitly warns against repeatedly polling GET /api/contracts/<id> and points at webhooks instead.
  • Webhook delivery: 15-second timeout, retried hourly up to six times.

Worth knowing

  • Because `test` is a per-request parameter rather than a property of the key, one missing field turns a staging run into contracts sent to real signers and billed.
  • Webhooks carry an `X-Signature-SHA256` HMAC-SHA256 header that has to be verified, and they arrive from a fixed list of eight IP addresses, which is what an outbound allowlist needs.
  • Requests made from a browser are rejected by CORS on purpose, to keep the Secret Token off the client, so there is no browser-side integration path.
  • Templates are markdown: POST /api/templates takes `title` and `markdown`, so document content is authored as text rather than uploaded as a PDF.

Checked against eSignatures.com API (2026-09-29), eSignatures.com (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.

esignaturesio_get_api_contracts_by_contract_idREAD

Read one contract: its status, title, labels, metadata, the signed PDF's URL once it exists, and every signer with their own signing page URL via GET /api/contracts/{contract_id}

api
esignaturesio_get_api_contracts_by_contract_id_contentREAD

Read the contract's document as markdown, which is what the content editing tool takes its `edits` against via GET /api/contracts/{contract_id}/content

api
esignaturesio_get_api_contracts_by_contract_id_placeholder_fieldsREAD

Read the values currently filling the contract's template placeholders via GET /api/contracts/{contract_id}/placeholder_fields

api
esignaturesio_get_api_contracts_recentREAD

List the 100 most recently created contracts on the account, each with its status and signers -- the discovery call that supplies the `contract_id` the other contract tools take via GET /api/contracts/recent

api
esignaturesio_get_api_templatesREAD

List the account's contract templates with their titles and labels -- the discovery call that supplies the `template_id` a contract is created from via GET /api/templates

api
esignaturesio_get_api_templates_by_template_idREAD

Read one template with its title, labels, placeholder keys and signer field ids -- the keys a contract created from it may fill via GET /api/templates/{template_id}

api
esignaturesio_get_api_templates_by_template_id_collaboratorsREAD

List the people who may edit this template in the eSignatures.com editor via GET /api/templates/{template_id}/collaborators

api
esignaturesio_get_api_templates_by_template_id_contentREAD

Read the template's document as markdown, which is what the content editing tool takes its `edits` against via GET /api/templates/{template_id}/content

api
esignaturesio_post_api_contractsWRITE

Create a contract from a template and send it for signature, or save it as a draft; the signers, the values that replace the template's placeholders, the signing order, the delivery methods and the multi-factor checks are all set here. Set `test` to `yes` to create a free test contract that is not legally binding and does not count against the plan via POST /api/contracts

api
esignaturesio_post_api_contracts_by_contract_id_contentWRITE

Apply find-and-replace edits to a contract's markdown document; send `dry_run` first to see what each edit would match before it is committed via POST /api/contracts/{contract_id}/content

api
esignaturesio_post_api_contracts_by_contract_id_deleteWRITE

Delete a contract and the document behind it from the account via POST /api/contracts/{contract_id}/delete

api
esignaturesio_post_api_contracts_by_contract_id_generate_pdf_previewWRITE

Render the contract as it currently stands to a PDF and return a link to it, without sending anything to a signer via POST /api/contracts/{contract_id}/generate_pdf_preview

api
esignaturesio_post_api_contracts_by_contract_id_placeholder_fieldsWRITE

Replace the values filling a contract's template placeholders, with text, markdown or another template via POST /api/contracts/{contract_id}/placeholder_fields

api
esignaturesio_post_api_contracts_by_contract_id_send_draftWRITE

Send a contract that was created with `save_as_draft`, which starts the signature requests to its signers via POST /api/contracts/{contract_id}/send_draft

api
esignaturesio_post_api_contracts_by_contract_id_signersWRITE

Add a signer to an existing contract with their delivery methods, signing order and multi-factor checks, and get their signing page URL back via POST /api/contracts/{contract_id}/signers

api
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_idWRITE

Change one signer's name, email, mobile, company, delivery methods, signing order or multi-factor checks on a contract that has not been signed via POST /api/contracts/{contract_id}/signers/{signer_id}

api
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_id_deleteWRITE

Remove one signer from a contract, invalidating their signing page and any signature request already delivered to them via POST /api/contracts/{contract_id}/signers/{signer_id}/delete

api
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_id_send_contractWRITE

Send one signer's signature request again, by email or SMS, to a signer who has not signed yet via POST /api/contracts/{contract_id}/signers/{signer_id}/send_contract

api
esignaturesio_post_api_contracts_by_contract_id_withdrawWRITE

Withdraw a contract that is already out for signature, cancelling it for every signer who has not signed yet and invalidating their signing pages via POST /api/contracts/{contract_id}/withdraw

api
esignaturesio_post_api_templatesWRITE

Create a reusable contract template from a markdown document, whose `{{key}}` placeholders become the fields a contract fills in via POST /api/templates

api
esignaturesio_post_api_templates_by_template_idWRITE

Change a template's title or its labels via POST /api/templates/{template_id}

api
esignaturesio_post_api_templates_by_template_id_collaboratorsWRITE

Invite someone by email to edit this template in the eSignatures.com editor via POST /api/templates/{template_id}/collaborators

api
esignaturesio_post_api_templates_by_template_id_collaborators_by_template_collaborator_id_removeWRITE

Revoke one collaborator's access to edit this template via POST /api/templates/{template_id}/collaborators/{template_collaborator_id}/remove

api
esignaturesio_post_api_templates_by_template_id_contentWRITE

Apply find-and-replace edits to a template's markdown document; send `dry_run` first to see what each edit would match before it is committed via POST /api/templates/{template_id}/content

api
esignaturesio_post_api_templates_by_template_id_deleteWRITE

Delete a template from the account; contracts already created from it are not affected via POST /api/templates/{template_id}/delete

api
esignaturesio_post_api_templates_by_template_id_duplicateWRITE

Copy a template under a new title, optionally into ANOTHER eSignatures.com account by naming that account's Secret Token as `target_secret_token` via POST /api/templates/{template_id}/duplicate

api

Put eSignatures.com behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.