E-Signature API Quickstart: SDK, Docs and Your First Call

For developers.

If you run a booking system, a website, or an app of your own, it can send agreements through SignSealer the same way the portal does. This video goes from nothing to your first document sent from code, in three parts: a key, the documentation, and the call itself. It starts under Developers.

Make a test key first. It acts on a sandbox, a copy of your account, so documents are prepared and sent exactly as they are live, but nothing reaches anybody, and nothing is billed. Give it a name, and make it. The key is shown once, and only a hash of it is kept, so copy it now.

The quickstart takes you from a key to a signed document, one step at a time. And every route in the reference is generated from the API's own definitions, so the documentation cannot drift from what the API actually does.

For JavaScript and TypeScript there is an SDK, with no dependencies at all. It retries the failures worth retrying, with an idempotency key, so a network blip never sends a second waiver. And when something is refused, it hands you the API's own sentence saying why.

Here is the whole thing. Prepare a document from a published template, with its blanks filled in for this booking. Then send it. Each signer gets a private link of their own, and it comes back to you once, in the response. The key is read from an environment variable: keep it on your server, never in a web page or an app.

Run it with the test key, and back comes the document's id and the signer's link. In the sandbox nothing is delivered. With a live key, the same call emails the guest, and the document appears in Documents, with the same trail and the same certificate as one sent by hand.

And if your website runs on WordPress, the SignSealer plugin sends documents and shows who has signed, with no code at all. Each of these has a guide of its own.