Use the API
Create, send and follow documents from your own software with the Sealsimple REST API, and download the signed PDF and audit trail. Live keys need Pro; test keys, to try it out, work on every plan.
Ovaj članak još nije preveden, pa se prikazuje na engleskom.
Na ovoj stranici
With the REST API your own software (a CRM, an HR system, a booking tool) can do what you do in the app: upload a document, add signers, place the fields, send it, and later fetch its status, the signed PDF and the audit trail. Live keys are part of Pro: they work while one of the workspace's owners has Pro. Test keys work on every plan, Free included. Only owners and admins can create API keys.
Create an API key
- Open Settings & branding in the account menu and go to API keys.
- Press Create API key and give it a name (for example the system that will use it).
- Choose Live key (Pro) or Test key (every plan), then press Create key.
- Copy the key straight away. It starts with
sk_live_orsk_test_and is shown only once: we keep only a fingerprint of it.
Treat a key like a password: keep it on your server, never in a web page or an app on someone's phone. Revoke stops a key at once. A key also stops working when the person who created it is no longer an owner or admin of the workspace.
Try it with a test key
- A test key only makes test documents, and a live key never sees them. In the app they have a TEST badge.
- Nobody is emailed. Once a test document is sent, the API gives each signer's signing link (
signing_url): open it to sign as that signer. - The signing page and every page of the signed PDF say TEST: it isn't a valid signature.
- Test documents don't count toward the free plan's monthly documents, don't send webhook events, and are deleted 7 days after they were made.
Ready for real documents? Create a live key on Pro; your code stays the same.
What the API can do
- Create a document from a PDF (or a PNG or JPEG image), with its signers, people who get a copy, a message, a subject, a deadline and the signing order. The fields are placed automatically, as with Place fields automatically in the editor; where nothing is found, each signer gets a signature, name and date at the end of the last page.
- Send a draft, remind the signers whose turn it is, or cancel a document.
- List documents and read one document's status, with when each signer opened and signed it.
updated_afterlists only what changed since your last check. - Download the signed PDF once everyone has signed, and read the audit trail.
- Add and remove webhooks, so an integration such as Zapier, Make or n8n can subscribe to document events itself (live keys only).
Word files can't be sent through the API: they're converted in the app, in your browser. Save them as PDF first.
Everything the API does is in the document's audit trail with the key's name, such as api:CRM integration, and the document shows up in the app like any other. Sending through the API goes through the same checks as the app.
Get notified instead of asking
To hear when a document is signed or completed without asking the API again and again, add a webhook: Send document events to your system with webhooks.
Reference
The API documentation lists every endpoint with examples, the error codes and the rate limit (60 requests a minute per key).