Contracts
The Contracts API provides CRUD access to contracts (signable documents), plus ancillary actions for tags and cloning.New to the API? Start with Getting started (base URL, response envelope, errors, pagination) and Authentication (API keys). Those conventions apply to every endpoint below and are not repeated here.
Identifier note: contracts are addressed by their numericdoc_id. Wherever{id}appears below it is thedoc_id.
Scope: signing (team/client/guest/in-person), publishing & emailing, automation, estimate generation and the rich document editor are managed in-app and are not part of this API. Signature/automation state is exposed read-only where relevant.
The contract object
List / search contracts
Query parameters
Example request
Example response — 200 OK
Get a contract
200) with message “Contract retrieved successfully.”
Create a contract
doc_body to set the content
directly, or contract_template to seed the body from a template. (Automation is not
configurable via the API; new contracts are created with automation disabled.)
Body parameters
Example request
Example response — 201 Created
Update a contract
200) with message “Contract updated successfully.”
Delete a contract
Example response — 200 OK
Set tags
tags array is the full set — it replaces existing tags; an empty array clears them.
200) with message “Contract tags updated successfully.”
Clone a contract
201) with message “Contract cloned successfully.”