Skip to main content
The Suresign REST API lets your own software read the documents in your workspace and download their PDFs. Use it to copy completed agreements into your file storage, attach them to a customer record, or build a report of what is signed and what is still waiting. The API is read-only: sending, signing and the agent all happen in the Suresign app.
The API is available on the Pro and Business plans and uses workspace API keys.

Base URL

Every request needs an Authorization: Bearer dtd_... header. See Authentication.

Endpoints

Full request and response details are in the API Reference section of the sidebar.

Pagination

GET /api/v1/documents uses cursor pagination. Ask for up to 100 documents at a time with limit (default 25). If there are more, the response includes a nextCursor. Pass it as cursor to get the next page. When nextCursor is null, you have everything.
List completed documents
Response (shortened)

Downloads

GET /api/v1/documents/{id}/download returns a PDF. Choose the file with type: Asking for signed or certificate before everyone has finished returns 404 with a message saying the document is not complete. Every API download is recorded in the document’s audit trail under the name of your API key.

Limits and errors

  • Rate limit: 300 requests per minute per key. Going over returns 429.
  • Deleted documents never appear in the API.
  • A document from another workspace returns 404, the same as one that does not exist.
  • Errors are JSON with an error message. See the error table in Authentication.

A common pattern

1

Wait for a webhook

Your webhook endpoint receives document.completed.
2

Download the signed PDF

Call GET /api/v1/documents/{id}/download with the document ID from the event.
3

Store it

Save the PDF, and the certificate if you want it, in your own system.

Next steps

Authentication

Create your API key.

Webhooks

Get told when documents change.