# SignSealShip Docs

## Docs

- [SignSealShip docs: sign, seal, and verify closing documents](https://docs.signsealship.com/index.md): Sign, notarize, and ship documents with verifiable cryptographic evidence. Build Verified Closing Rooms and seal Closing Passports over the partner API.
- [SignSealShip API quickstart: seal your first passport](https://docs.signsealship.com/quickstart.md): Go from requesting access to a sealed Closing Passport: get a partner key, create a Closing Room, attach orders, share the room link, and seal the passport.
- [Verified Closing Rooms: shareable live-status closing pages](https://docs.signsealship.com/closing-rooms.md): One shareable, live-status page per closing: how Verified Closing Rooms work, why the link is a bearer credential, how rotation works, and per-tier room quotas.
- [Closing Passport: sealed evidence manifests per room](https://docs.signsealship.com/closing-passport.md): How the Closing Passport works: a versioned, KMS-sealed evidence manifest per room with canonical JSON, hash chain, public verification, and coverage statement.
- [Partner analytics: order flow and evidence coverage](https://docs.signsealship.com/analytics.md): Use the partner analytics dashboard to read a live 90-day view of order volume, lifecycle stage, turnaround, service use, evidence inventory, and revenue.
- [Evidence model: SEALED, RECORDED, and verification](https://docs.signsealship.com/evidence-model.md): The vocabulary behind every SignSealShip evidence claim: what SEALED, RECORDED, and no-evidence-yet cryptographically mean, and how to verify without trust.
- [Webhooks guide: subscribe and verify events](https://docs.signsealship.com/webhooks-guide.md): Subscribe to passport.sealed, room.order_attached, and room.passport_sealed events, and verify the SignSealShip-Signature HMAC in Node and Python.
- [SignSealShip changelog: new features, updates, and fixes](https://docs.signsealship.com/changelog/overview.md): Weekly release notes for SignSealShip — new features, updates, and bug fixes across Closing Rooms, Closing Passports, and the partner API.
- [SignSealShip API overview and reference](https://docs.signsealship.com/api-reference/index.md): Overview of the SignSealShip partner API: create sign/notarize/ship orders, seal executed PDFs as Proof Passports, run Verified Closing Rooms, seal Closing Passports, and get signed webhooks.
- [Authenticate to the SignSealShip partner API](https://docs.signsealship.com/api-reference/authentication.md): Authenticate to the SignSealShip API with a partner bearer key, understand how keys are issued and rotated, and see every rate limit.
- [Partner access requests API: self-serve API key requests](https://docs.signsealship.com/api-reference/partner-requests.md): Request a SignSealShip partner API key self-serve — business emails with a clear use case get an instant trial key, and everything else is human-reviewed.
- [Order API: create, track, and pay sign/notarize/ship orders](https://docs.signsealship.com/api-reference/orders.md): Create sign, notarize, and ship orders for your clients' own completed documents, list and fetch them, and mint Stripe hosted checkout — priced server-side with your partner discount.
- [Partner analytics API: live order and evidence metrics](https://docs.signsealship.com/api-reference/analytics.md): Read a request-time analytics snapshot for your partner orders, including volume, lifecycle funnel, turnaround, service mix, evidence counts, and revenue.
- [Playbooks API: run registry-owned automations](https://docs.signsealship.com/api-reference/playbooks.md): List and start typed, registry-owned automations without allowing callers to inject workflow steps or source.
- [Closing Rooms API: create, attach orders, and rotate links](https://docs.signsealship.com/api-reference/rooms.md): Create Verified Closing Rooms, attach orders by public code, rotate bearer links, and read the live room view with progress, evidence badges, and activity.
- [Closing Passport API: seal and verify room manifests](https://docs.signsealship.com/api-reference/passports.md): Seal versioned, hash-chained Closing Passport manifests for a room and verify them publicly, with statusAtSnapshot, chainOk recompute, and coverage semantics.
- [Proof Passport API: seal executed PDFs with KMS](https://docs.signsealship.com/api-reference/proof-passport.md): Seal an executed PDF with Google Cloud KMS, gather RFC 3161 and OpenTimestamps evidence, and get a public verification URL — the Proof Passport API.
- [Webhooks API: manage subscriptions and signed events](https://docs.signsealship.com/api-reference/webhooks.md): Manage webhook subscriptions with your partner key or dashboard session, and handle passport, room, and order event payloads with SignSealShip-Signature HMAC checks.
- [Request partner access](https://docs.signsealship.com/api-reference/onboarding/request-partner-access.md): Request a partner API key self-serve. Public; rate limited to 5 requests per hour per IP. A business-domain work email plus a coherent, on-topic use case is issued a trial key instantly (emailed once); everything else is queued for human review. Both outcomes return 200.
- [Create an order](https://docs.signsealship.com/api-reference/orders/create-an-order.md): Create a sign / notarize / ship order for a client's own completed document. Send the PDF as the multipart part `document`, or reference a fill-online result with `fill_token` — exactly one of the two, never both. Pricing is computed entirely server-side from the B2B price book with your subscriptio…
- [List your orders](https://docs.signsealship.com/api-reference/orders/list-your-orders.md): List the orders created with your partner key, newest first. Rate limited with `partner-write` (60/min per key).
- [Fetch an order](https://docs.signsealship.com/api-reference/orders/fetch-an-order.md): Fetch one of your orders by its public code. Partner-scoped: another partner's order and an unknown code return the identical 404. Rate limited with `partner-write` (60/min per key).
- [Mint a checkout session](https://docs.signsealship.com/api-reference/orders/mint-a-checkout-session.md): Mint the Stripe hosted-checkout URL for a payable order. Minting never changes order state — state advances only via the verified Stripe webhook after payment clears. Rate limited with `partner-write` (60/min per key).
- [Create a room](https://docs.signsealship.com/api-reference/closing-rooms/create-a-room.md): Create a Verified Closing Room. Enforces your tier's active-room quota (trial and PartnerLink: 5 open rooms; ProOffice: 25; ClosingDesk: unlimited).
- [List your rooms](https://docs.signsealship.com/api-reference/closing-rooms/list-your-rooms.md): Returns your own rooms only, newest first.
- [Read the room (public)](https://docs.signsealship.com/api-reference/closing-rooms/read-the-room-public.md): Public read by possession of the room code — no API key. The same live JSON the room page renders. Codes outside the 24–64 character gate and unknown codes both return an empty 404. Responses are `Cache-Control: no-store`.
- [Attach an order](https://docs.signsealship.com/api-reference/closing-rooms/attach-an-order.md): Attach an order to a room. Authorization is possession of the order's public code. Idempotent — re-attaching succeeds with `alreadyAttached: true`. A room holds at most 50 orders.
- [Detach an order](https://docs.signsealship.com/api-reference/closing-rooms/detach-an-order.md)
- [Rotate the room link](https://docs.signsealship.com/api-reference/closing-rooms/rotate-the-room-link.md): Reissue the room's bearer code. Every previously shared link dies instantly — the mitigation for a leaked or over-shared link.
- [Seal a passport version](https://docs.signsealship.com/api-reference/closing-passports/seal-a-passport-version.md): Mint the next Closing Passport version for a room — a dated, hash-chained, KMS-sealed snapshot, never an overwrite. Capped at 20 versions per room. Requires your partner key; the room must be yours.
- [Verify a passport (public)](https://docs.signsealship.com/api-reference/closing-passports/verify-a-passport-public.md): Public verification of a Closing Passport version. `chainOk` is recomputed on every call, never a stored verdict. Malformed and unknown codes return the identical generic 404 `{"verdict": "unknown"}`.
- [Download the sealed certificate (public)](https://docs.signsealship.com/api-reference/closing-passports/download-the-sealed-certificate-public.md): Streams the sealed Closing Passport certificate PDF. The verify code is the bearer.
- [Seal a document](https://docs.signsealship.com/api-reference/proof-passport/seal-a-document.md): Submit a finished, signed PDF (multipart part named `file`, up to 35 MB). It returns sealed with Google Cloud KMS, timestamped by independent RFC 3161 and OpenTimestamps authorities, and wrapped in a public verification URL. Bytes are streamed in memory, never to disk, and discarded after sealing.
- [Fetch a passport](https://docs.signsealship.com/api-reference/proof-passport/fetch-a-passport.md): Fetch a Proof Passport you created. Partner isolation is enforced — a passport is visible only to the partner that created it.
- [Verify a passport (public)](https://docs.signsealship.com/api-reference/proof-passport/verify-a-passport-public.md): Public, self-contained verification of a Proof Passport. Never exposes the partner identity. Malformed and unknown codes return the identical generic 404 `{"verdict": "unknown"}`.
- [Download the sealed document (public)](https://docs.signsealship.com/api-reference/proof-passport/download-the-sealed-document-public.md): Streams the byte-identical sealed PDF. Any holder of the code can fetch it; the file also verifies on its own in any PDF reader's signature panel.
- [Register a passport webhook](https://docs.signsealship.com/api-reference/webhooks/register-a-passport-webhook.md): Register an https endpoint for `passport.sealed` events using your partner API key. The signing secret is returned exactly once — only its hash is stored. Subscriptions created this way receive only `passport.sealed` (no room events).
- [List subscriptions](https://docs.signsealship.com/api-reference/webhooks/list-subscriptions.md): List your partner's webhook subscriptions, newest first. Accepts your partner API key (`Authorization: Bearer sss_pk_...`) for server-to-server management, or the SignSealShip dashboard session cookie (`__Host-session`) — link a session once with a partner key at https://signsealship.com/partner.
- [Create a subscription](https://docs.signsealship.com/api-reference/webhooks/create-a-subscription.md): Create a topic-aware webhook subscription. Accepts the partner API key or the dashboard session cookie. The signing secret is shown exactly once. Order topics (`order.created`, `payment.cleared`, `signature.completed`, `shipment.delivered`) deliver only for orders you created through the Order API.
- [Delete a subscription](https://docs.signsealship.com/api-reference/webhooks/delete-a-subscription.md): Delete a subscription. Accepts the partner API key or the dashboard session cookie.
- [Rotate a signing secret](https://docs.signsealship.com/api-reference/webhooks/rotate-a-signing-secret.md): Reissue the subscription's signing secret. The new secret is returned exactly once — only its hash is stored. For 24 hours deliveries are signed with both the old and the new secret (one `v1` entry each in the `SignSealShip-Signature` header), so your endpoint can cut over without dropping verificat…
- [List delivery attempts](https://docs.signsealship.com/api-reference/webhooks/list-delivery-attempts.md): A metadata-only feed of the subscription's recent delivery attempts — what was attempted, when, and how your endpoint answered. Event payload bodies are never stored or returned. Accepts the partner API key or the dashboard session cookie.

## OpenAPI Specs

- [openapi](https://docs.signsealship.com/api-reference/openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.