If you build software for businesses, like a booking system or a point of sale, your customers' guests can sign inside your product, without leaving it and without an email. It starts with a key, made under Developers. A test key works on a sandbox, so nothing reaches anybody while you build.
For platform partners and developers.
If you build software for businesses, like a booking system or a point of sale, your customers' guests can sign inside your product, without leaving it and without an email. It starts with a key, made under Developers. A test key works on a sandbox, so nothing reaches anybody while you build.
With the SignSealer SDK for JavaScript and TypeScript, it takes two calls. Prepare the document from a published template, then send it with the delivery set to embedded. Nothing is emailed or texted. The link comes back to you, once, for your own product to show. The key stays on your server, in an environment variable, never in a web page or an app.
Run it, and there is the link.
Open that link in a frame on your page, or a web view in your app, and your guest meets the same signing page as everybody else: the whole document to read, consent to sign electronically, and the signature, recorded the same way and sealed with the same certificate.
The embedding guide covers the rest: which sites may frame the page, where the guest is sent when they finish, and the webhook that tells your system it is signed.
Not writing JavaScript? Each SDK call is one request to the REST API, so the same two steps work from PHP, Python, Ruby, .NET, or anything that can make a web request. The reference lists every route, generated from the API itself.