Skip to main content
POST
Preview moving a pitch into a client workspace

Authorizations

Authorization
string
header
required

A Searchable API key, created under Manage Account → Integrations → API Keys. Send as Authorization: Bearer sea_xxxxx. Every key carries one or more scopes (read, write, admin) and may optionally be bound to a single project — see Getting started.

Path Parameters

pitchId
string<uuid>
required

The pitch's id, from GET /api/mcp/pitches. A pitch is a project, so its id works with every project endpoint too.

Body

application/json
destination
object
required

Where the pitch would go. A new client's preview needs only its staff, if any.

Response

The preview of the move.

What the move would do; nothing changed. An existing destination also carries project, destinationWorkspace, accessCarrierSummary and the previewSignature the move takes back; a new client's preview has the source side alone.

destination
object
required
counts
object
required

What moves with the pitch: prompts, visibilityReports, sharedReports, contentPieces, conversations, messages, agentRuns, projectMembers, ga4Links and gscLinks, each a count.

warnings
object[]
required

What the user must confirm before the pitch moves: send exactly these codes as acknowledgedWarnings.

blockers
object[]
required

What stops the move: it is refused until none remain.

previewSignature
string

An existing destination only: pass it back unchanged with the move.

project
object

An existing destination only: the pitch (id, name, domain, sourceWorkspace).

destinationWorkspace
object

An existing destination only: the workspace (id, name, slug, owner, workspaceType, plan fields where you may see billing, and usage against its limits).

accessCarrierSummary
object

An existing destination only: the access grants (willBeRemoved) and bindings (willMove) the move affects, by category.