Skip to main content
POST
Creates a new conversation with flexible user identification.

Authorizations

x-api-key
string
header
required

Copy the API key as provided by the Bridge Console.

Path Parameters

workspaceId
string<uuid>
required

Unique identifier of the workspace (UUID v4).

Example:

"b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234"

Body

application/json

Request body for creating a new conversation.

participants
Participants · object
required

Participants to add to conversation.

name
string | null

Optional name/title for the conversation.

Example:

"Bridge Support Team"

status
enum<string>
default:ACTIVE

Initial conversation status - 'active' for visible conversations, 'ghost' for invisible until first interaction.

Available options:
ACTIVE,
GHOST,
RELEASED,
NOT_ASSIGNED_TO_HUMAN,
BLOCKED
Example:

"ACTIVE"

teamId
string<uuid> | null

Team UUID for round-robin assignment (optional, mutually exclusive with internalParticipants).

Example:

"9fd1468d-e5ca-4ba3-98d1-13017e6f3808"

onboardingTemplates
OnboardingTemplateRequest · object[]

Ordered templates to open the conversation with. They replace the workspace's configured onboarding sequence for this conversation, either entirely or only its first template, depending on how the workspace is set up; in the second case the rest of the configured sequence is still sent after yours. Position implies order. Omit to keep the workspace default. Each template must exist, belong to your workspace or the platform scope, and — for WhatsApp provider templates — be approved by Meta for the WhatsApp Business Account behind the line each participant is reached on; otherwise the request is rejected and no conversation is created. A template whose variables need values only you can provide takes them in the entry's parameters. If one of the configured templates sent after yours needs values only the caller can provide, the request is rejected with 422 BRIDGE_CONVERSATION_0608, with extra.templateId naming that template and extra.origin set to WORKSPACE_CONFIGURATION. Changing the request will not help: ask a workspace admin to change the onboarding sequence.

Response

Successful Response

Response body for conversation details.

id
string
required

Unique identifier of the conversation (UUID v4).

Example:

"b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234"

workspaceId
string
required

Unique identifier of the workspace (UUID v4).

Example:

"b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234"

participants
Participants · object
required

Participants of the conversation.

createdAt
string<date-time>
required

Timestamp when the conversation was created.

Example:

"2003-04-10T09:00:00.000Z"

updatedAt
string<date-time>
required

Timestamp when the conversation was last updated.

Example:

"2003-04-10T09:00:00.000Z"

name
string | null

Optional name/title for the conversation.

Example:

"Bridge Support Team"

status
enum<string> | null

Current conversation status - 'ACTIVE' for visible conversations, 'GHOST' for invisible until first interaction.

Available options:
ACTIVE,
GHOST,
RELEASED,
NOT_ASSIGNED_TO_HUMAN,
BLOCKED
Example:

"ACTIVE"