Reference
Roadmap and current limits
The API covers one job well — getting a document signed — and does not pretend to cover more. Here is what it cannot do, so you can find out now rather than halfway through building.
Nothing here has a date
These are gaps, not commitments. If one of them blocks you, tell us — what integrators actually ask for is what gets built next.
Not available today
| Not supported | Details |
|---|---|
| Uploading or downloading files | There is no endpoint to upload a PDF, and no way to fetch the signed PDF or its certificate. Documents created through the API are generated from the title and recipients you supply. Retrieve finished documents from the web app. |
| Placing signature fields | Field and annotation placement is not exposed. content accepts only a small metadata bag — a message, the signing order, and an expiry — and unknown properties are dropped rather than rejected. |
| Updating or deleting anything | The API is create, read, and send only. There is no PATCH, PUT, or DELETE on any resource: you cannot edit a draft, change a recipient, void a document, or delete one. |
| Templates | Templates are invisible to v1. A template id returns 404 from every documents endpoint, and there is no way to create a document from one. |
| Everything outside documents | Clients, projects, the Compliance Vault, certificates of insurance, notices to owner, and the whole money surface — invoices, pay applications, change orders — have no API. They exist only in the web app. |
| Bulk send | Sending one document to many recipient sets in one call is not exposed. Loop over individual creates and sends, minding the rate limits. |
| Browser access | No CORS headers are sent, so the API cannot be called from browser JavaScript. This is intentional: doing so would put your API key in the page. |
| Key rotation via API | Keys are issued and revoked in Settings. There is no endpoint to mint, rotate, or list them, so rotation cannot be automated end to end. |
| A real sandbox | Test keys suppress delivery but operate on production data. There is no isolated dataset to experiment against. |
Webhooks are available
Outbound webhooks — a signed callback when a document is sent, viewed, signed, completed, declined, or voided — are live. See webhooks. Endpoints are managed in Settings rather than through the API, which is the one gap here: an API key cannot register or redirect your webhook endpoints, deliberately.
What will not change
The stability contract — what may change inside v1 without warning, what forces a new version, and how to write a client that survives both — lives on versioning.