Documentation menu

Platforms and partners

A point-of-sale system, a property manager, a booking engine: your product has customers of its own, and each of them signs waivers or agreements. This page is how that works, and who pays whom.

How your customers get credentials

Every business you serve is a business in SignSealer — its own templates, documents, evidence and team, isolated from every other by the database rather than by your code. Today each one connects the same way any customer does: somebody at that business signs in to the portal, opens Developers, and creates an API key with the scopes your integration needs (signing:read and signing:write for most). Your product stores that key for that business and sends it as Authorization: Bearer. Keys are scoped, revocable, and shown once; the authentication page has the details.

Or your product asks the business once. Send the person to /oauth/authorize, they agree on a consent screen that shows your registered name and the scopes you asked for, and your server exchanges the code at /oauth/token for an access token that works for an hour and a refresh token that gets the next one. It is standard OAuth 2.0 with PKCE; any client library speaks it, and the authentication page has the two requests in full. The business can end the connection under Developers → Connected apps whenever it likes. Nothing about the key-based path changes.

Billing your customers once

You do not want your customer to pay you and then pay us. So a business can be billed through a partner: it pays SignSealer nothing, its billing page says who bills it, checkout is refused to it, and its completed agreements roll up onto your monthly statement at a wholesale rate agreed with us, plus an optional monthly fee per business. What you charge your own customer is yours to decide. Nothing about sending or evidence changes; a partner-billed business is never refused for a billing reason.

To set it up, we register your product as a partner (the same record the install flow uses), agree the rates, and mark each of your businesses as billed through you. Email partners@signsealer.com with your product's name, a contact, and the businesses to move.

What stays the same

  • Isolation. A key for one business reaches that business and no other, whoever holds it.
  • Evidence. The certificate, the trail and the sealed PDF belong to the business that sent the document, and it can download them without you.
  • Webhooks. Register your endpoint per business, or one endpoint that reads the business from the payload; either way the signature is per business.
  • The signer's experience. The signing page is ours and is served by us; embed the link, text it, or open it on a tablet. It loads nothing from anywhere and cannot be framed.

Ready to build? An API key takes a minute in the portal, and the free plan covers the first 25 agreements a month.

Get an API key