Skip to main content
The TrailerCast API is a read-only, REST-style API for the data TrailerCast captures during a sale, plus signed webhooks that tell your system the moment something happens. It is the same interface TrailerCast’s own CRM integration is built on.

Quickstart

Create a key, make your first request, and receive your first webhook in about ten minutes.

Authentication

Workspace-scoped API keys, what they can and cannot do, and how to rotate them.

Webhooks

Event types, the envelope, signature verification, and delivery guarantees.

Endpoints

Every endpoint, generated from the OpenAPI spec, with a try-it playground.

​
What you can read

​
What you can be told about

Register a webhook endpoint and TrailerCast pushes a signed event when:
  • a prospect does something (engagement.recorded)
  • an AI call summary is generated or regenerated (call.summary.created)
  • a Decision Room’s status, value, close date, or contact changes (decision_room.updated)
  • a tracked contract changes signature status (decision_room.esign.updated)
Webhooks are the doorbell; the endpoints above are the truth. The recommended pattern is to act on the webhook, then reconcile with the cursor-paginated endpoints — a dropped delivery costs latency, never data. See Syncing a CRM.

​
Core concepts

Everything in TrailerCast belongs to a workspace (your company). An API key is minted by a workspace and can only ever read that workspace. There is no way to name another workspace in a request, and an id that belongs to a different workspace returns 404, not 403 — the API never confirms it exists.
A completed recording — a demo, a discovery (“qualifying”) call, or an internal meeting — with its transcript-derived AI summary. Calls are identified by a UUID and carry updatedAt, which moves when the summary is regenerated.
The buyer-facing room a rep builds for one opportunity: trailers, documents, a mutual action plan, the buying committee, and a conversation thread. This is the object that maps most naturally to a deal in a CRM. Identified by a UUID (buyerSpaceId wherever it appears on other objects).
A per-recipient share link — the credential a prospect opens a trailer, document, or room with. It is how engagement is attributed to a named person: every event carries the distributionId it came through, and the actor on that event is the person the link was addressed to.
One prospect action, with a type, a timestamp, the actor, and the objects involved. Events have integer ids and are served in id order, which is what makes them safe to sync with a cursor.

​
Base URL

Your API host is shown on Settings → Integrations → API access next to your keys. For most workspaces it is https://trailercst-backend-production.up.railway.app.

​
Availability

The API is enabled per workspace. If a request returns 403 FEATURE_NOT_ENABLED, it is not yet turned on for your workspace — contact hello@trailercast.io.
Read-only. There is no endpoint that creates or changes anything in TrailerCast. Writes — deals, notes, tasks — belong in your system of record; TrailerCast supplies the buyer-side evidence.