Enterprise API and Webhooks
Use the document signing API
Enterprise systems can create a Signrrett signing request, add recipients and fields, then send it for signature.
Steps to follow
- 1
Create an Enterprise API key with documents:write for creating and sending requests.
- 2
Use documents:read too if the outside system needs to check status or pull final download details.
- 3
Send a multipart POST request to /api/v1/signing-requests with title, a PDF file, optional recipients JSON, and optional fields JSON.
- 4
Recipients JSON should include name, email, role, and optional signing_order.
- 5
Fields JSON should include field_type, assigned_recipient_email, page_number, x, y, width, height, and required.
- 6
Use the prepare_url returned by the API if a team member needs to review or adjust recipients and fields in Signrrett.
- 7
Send a unique Idempotency-Key header on create and send requests so a network retry does not create a duplicate document or invitation.
- 8
Call POST /api/v1/signing-requests/{id}/send when the document is ready to generate signing links and, when send_emails is true, notify recipients.
- 9
Use GET /api/v1/signing-requests/{id} to check status, recipient progress, signing links, and final download availability.
- 10
Configure the document events your system needs. The Developer page lists every currently supported event instead of a partial event list.
- 11
For a controlled test, send { send_emails: false } to generate signing links without emailing recipients.