What the platform does
Sign
First-party e-signature with signed audit trails. Signers work from a link — no accounts required.
Seal
Executed documents are sealed with an asymmetric Google Cloud KMS signature and byte-range tamper evidence, then timestamped by independent authorities.
Ship
Physical originals move by tracked carrier, and tracking status appears on the order and in its Closing Room.
Prove
Every seal gets a public verification URL. Anyone — a counterparty, an auditor, a court — can check it without a SignSealShip account.
Start here
Quickstart
Request access, get your partner key, and go from zero to a sealed Closing Passport with a handful of curl commands.
API reference
Every endpoint: authentication, rooms, passports, webhooks, and the request and response shapes they pin.
Learn the concepts
Closing Rooms
One live-status page per closing: rooms, bearer links and rotation, tiers and quotas.
Closing Passport
The versioned, sealed evidence manifest for a room — hash-chained, publicly verifiable, honest about its coverage.
Evidence model
What SEALED, RECORDED, and “no evidence yet” each mean, and how to verify claims without trusting us.
Webhooks
Subscribe to events and verify the signed deliveries with a complete recipe in Node and Python.
Honest boundaries
The evidence in these docs is cryptographic fact, not legal advice. SignSealShip never claims evidence it does not hold: statuses shown in a room are our live records, sealed hashes are independently verifiable artifacts, and every Closing Passport states exactly what it does and does not cover.API access is granted per partner. Request a key at signsealship.com/partner — see the quickstart for the full flow.