> ## Documentation Index
> Fetch the complete documentation index at: https://docs.signsealship.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SignSealShip changelog: new features, updates, and fixes

> Weekly release notes for SignSealShip — new features, updates, and bug fixes across Closing Rooms, Closing Passports, and the partner API.

Recent changes to SignSealShip. For breaking changes and API-level details, see the [API reference](/api-reference).

<Update label="Partner analytics GA + playbooks limited release" description="August 2, 2026" tags={["Partner API", "Analytics", "Automation"]}>
  ## New

  **Partner analytics is generally available.** The partner portal now has a request-time, tenant-scoped 90-day view of order volume, current lifecycle funnel, paid-to-completed turnaround, service mix, revenue, and the evidence artifacts attached to the cohort. Evidence counts lead the product view and keep their exact semantics: sealed/notarized document rows and delivered shipment rows, not an inferred coverage percentage. Open [Partner analytics](/analytics), or read the complete [analytics API contract](/api-reference/analytics) for a selectable 1–366-day window and every funnel status.

  **Playbooks API (limited release).** Partners with access can list registry-owned automations and start them with typed form parameters. Callers select a registered key but can never submit workflow source or inject steps; values are validated and passed only as runtime arguments. The first playbook, `approval_gate`, waits up to 30 days for a human decision and resolves expired waits as `expired`. Playbooks are disabled by default, and both endpoints return `404` until enabled for the account. See the [Playbooks API](/api-reference/playbooks).
</Update>

<Update label="Live shipping rates, mail evidence tiers, discount codes, standalone fax" description="August 1, 2026" tags={["Orders", "Shipping", "Pricing", "Partner API"]}>
  ## New

  **Live carrier rates at checkout.** Shipping is now rate-shopped against the destination address at order time: customers pick a speed tier with the real price and the carrier's delivery date, postage is passed through at the quoted rate, and a disclosed handling fee is added on top. On the Order API this changed the quote shape — shipping is now **two lines**, `ShippingCarrierRate` + `ShippingHandlingFee`, and the postage amount varies by address. Flat-rate shipping is gone.

  **Print & mail evidence tiers.** "We print and mail it" now offers three mail classes, described by the proof they produce: Standard (no delivery proof), Certified (USPS proof of delivery), and Certified + return receipt (signed receipt returned to your record).

  **Discount codes.** Percentage and fixed-amount codes, applied at quote time and redeemed exactly once when payment clears. They appear on quotes and orders as a negative-amount `Discount` line.

  **Standalone fax.** A fax with a sealed transmission certificate can now be ordered on its own — supplying a destination number selects the service, and a fax-only order is priced as fax only.

  ## Fixed

  * `GET /api/partner/me` with no credential now returns `401` (previously `403`). `403` is reserved for a valid session that has not linked a partner yet — the two cases were indistinguishable before.
  * The documented `lines` example and the `services` field shape in the API reference were corrected to match what the API actually returns (PascalCase line types; `services` is a comma-separated flags string on order responses).
</Update>

<Update label="Order API + order webhooks" description="July 17, 2026" tags={["Partner API", "Orders", "Webhooks"]}>
  ## New

  **Order API.** Partners can now place full sign / notarize / ship orders with their API key. [`POST /api/partner/orders`](/api-reference/orders#create-an-order) takes the client's own completed PDF (or a fill-online `fill_token`), prices the order server-side from the B2B price book with the partner's subscription-tier discount applied automatically, and can mint the Stripe hosted-checkout session in the same call. List orders with `GET /api/partner/orders`, fetch one with `GET /api/partner/orders/{code}`, and mint checkout later with `POST /api/partner/orders/{code}/checkout`. Order state advances only via the verified Stripe webhook — minting a checkout session or landing on the success page never changes state. See the [Order API guide](/api-reference/orders).

  **Order webhooks.** Four new subscribable topics — `order.created`, `payment.cleared`, `signature.completed`, and `shipment.delivered` — deliver for orders created through the Order API, signed exactly like existing deliveries and echoing the partner's `external_reference` for correlation. See [webhooks](/api-reference/webhooks#order-events).

  **API-key webhook management.** The `/api/partner/webhooks` management routes now also accept the bearer partner API key (previously dashboard-session only), so subscriptions can be managed server-to-server — from your own provisioning code or a Zapier zap.

  ## Updates

  * New [`POST /api/partner/webhooks/{id}/rotate`](/api-reference/webhooks#rotate-a-signing-secret) reissues a subscription's signing secret — shown exactly once — with a 24-hour dual-signature overlap so endpoints cut over without dropping verification.
  * New [`GET /api/partner/webhooks/{id}/deliveries`](/api-reference/webhooks#list-delivery-attempts) returns a metadata-only feed of recent delivery attempts.
</Update>

<Update label="July 13, 2026" tags={["Admin", "Trust & Safety"]}>
  ## New

  **Agent actions review queue.** The admin hub has a new **Agent actions** page that lists every action an AI agent has proposed on a [Closing Room](/closing-rooms), with **Approve** or **Reject** on each one. Approve confirms before anything goes out (with an extra prompt when the action would send a partner update), and drafted content is displayed safely — never rendered as HTML.

  **Pending actions on the admin hub.** The admin home now shows an **Agent actions** tile with a live pending count, so reviewers can see at a glance whether anything is waiting.

  ## Updates

  * When the concierge flags a Closing Room as needing human attention, the room is now automatically surfaced in the review queue as an internal note. Nothing is sent externally — it just makes the flagged closing easy to find and act on.
  * Approving a partner update from the queue continues to use server-resolved recipients and the once-only delivery guarantee shipped earlier this week, so agents still can't choose who a message goes to.
</Update>

<Update label="July 13, 2026" tags={["Trust & Safety", "Concierge"]}>
  ## New

  **Human review before anything leaves a Closing Room.** When the concierge or another agent wants to take an outbound action on a room — for example, sending a partner update — that action is now proposed to an admin queue first. A human approves or rejects it, and only approved actions are executed. Agents never send on their own and never choose the recipient.

  **Server-resolved recipients for partner updates.** For approved partner updates, SignSealShip resolves the destination from the [Closing Room](/closing-rooms) itself — not from anything an agent supplied. Partners keep receiving updates the same way; the recipient is just guaranteed to be the room's partner contact of record.

  ## Updates

  * Approved partner updates are sent exactly once. Retrying an approval will not resend the message.
  * Every partner update includes a compliance note so recipients can tell it went through review.
  * Internal-only notes are supported as a separate action type, so admins can capture context on a room without sending anything externally.
</Update>

<Update label="July 13, 2026" tags={["Concierge", "Partner API"]}>
  ## New

  **AI concierge, in every Closing Room.** A first-party AI assistant is now available directly inside [Closing Rooms](/closing-rooms). Signers and partners can ask about e-signing, notarization, shipping, and order status — and hand off to a human at any time. No third-party scripts, no cookies.

  **Closing health advisory (partner-only).** Partner dashboards now show a **Closing health** pill on each room — green ("On track"), amber ("Needs attention"), or red — with a short headline and detail. It's AI-drafted from live room state (order stages, signer progress, whether a [Closing Passport](/closing-passport) is sealed) and clearly labeled as a working note, not legal advice. Rooms without an advisory yet simply don't show the card, so nothing changes for existing views.

  ## Updates

  * The concierge is now grounded in live room data. It reads room status, every attached order with its live stage and requested services, and whether a Closing Passport is sealed, so its answers match what partners see in the dashboard.
  * Every advisory carries a timestamp and a "needs human review" flag when the concierge is uncertain, so nothing gets over-claimed.
  * Order stages surfaced in concierge replies now use plain-English labels (for example, "Awaiting signatures", "Notarization scheduled", "Shipped") instead of internal status codes.

  ## Fixes

  * Room-level questions no longer fall back to per-order guesses when a room code is available. The concierge now reads the room directly and reports the full attached order set, including whether the room's [Closing Passport](/closing-passport) has been sealed.
</Update>


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