eSignatures.com
DOCS & KNOWLEDGE · FILES & DOCS
Contracts out for signature, their signers, templates, and PDFs in the account they connected.
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_idREADRead 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}
esignaturesio_get_api_contracts_by_contract_id_contentREADRead the contract's document as markdown, which is what the content editing tool takes its `edits` against via GET /api/contracts/{contract_id}/content
esignaturesio_get_api_contracts_by_contract_id_placeholder_fieldsREADRead the values currently filling the contract's template placeholders via GET /api/contracts/{contract_id}/placeholder_fields
esignaturesio_get_api_contracts_recentREADList 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
esignaturesio_get_api_templatesREADList 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
esignaturesio_get_api_templates_by_template_idREADRead 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}
esignaturesio_get_api_templates_by_template_id_collaboratorsREADList the people who may edit this template in the eSignatures.com editor via GET /api/templates/{template_id}/collaborators
esignaturesio_get_api_templates_by_template_id_contentREADRead the template's document as markdown, which is what the content editing tool takes its `edits` against via GET /api/templates/{template_id}/content
esignaturesio_post_api_contractsWRITECreate 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
esignaturesio_post_api_contracts_by_contract_id_contentWRITEApply 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
esignaturesio_post_api_contracts_by_contract_id_deleteWRITEDelete a contract and the document behind it from the account via POST /api/contracts/{contract_id}/delete
esignaturesio_post_api_contracts_by_contract_id_generate_pdf_previewWRITERender 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
esignaturesio_post_api_contracts_by_contract_id_placeholder_fieldsWRITEReplace the values filling a contract's template placeholders, with text, markdown or another template via POST /api/contracts/{contract_id}/placeholder_fields
esignaturesio_post_api_contracts_by_contract_id_send_draftWRITESend 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
esignaturesio_post_api_contracts_by_contract_id_signersWRITEAdd 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
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_idWRITEChange 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}
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_id_deleteWRITERemove 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
esignaturesio_post_api_contracts_by_contract_id_signers_by_signer_id_send_contractWRITESend 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
esignaturesio_post_api_contracts_by_contract_id_withdrawWRITEWithdraw 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
esignaturesio_post_api_templatesWRITECreate a reusable contract template from a markdown document, whose `{{key}}` placeholders become the fields a contract fills in via POST /api/templates
esignaturesio_post_api_templates_by_template_idWRITEChange a template's title or its labels via POST /api/templates/{template_id}
esignaturesio_post_api_templates_by_template_id_collaboratorsWRITEInvite someone by email to edit this template in the eSignatures.com editor via POST /api/templates/{template_id}/collaborators
esignaturesio_post_api_templates_by_template_id_collaborators_by_template_collaborator_id_removeWRITERevoke one collaborator's access to edit this template via POST /api/templates/{template_id}/collaborators/{template_collaborator_id}/remove
esignaturesio_post_api_templates_by_template_id_contentWRITEApply 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
esignaturesio_post_api_templates_by_template_id_deleteWRITEDelete a template from the account; contracts already created from it are not affected via POST /api/templates/{template_id}/delete
esignaturesio_post_api_templates_by_template_id_duplicateWRITECopy 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
Often connected alongside
Put eSignatures.com behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.