> ## Documentation Index > Fetch the complete documentation index at: https://docs.bridge.new/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Bridge exposes three integration surfaces: the REST Integrations API for pushing data into Bridge, webhooks for receiving events from Bridge, and the public Custom Connections endpoint that a tenant's landing page posts to. > The Integrations API host is https://api-connect-us.bridge.new and every request to it must be authenticated with the x-api-key header. Bridge does not use bearer tokens or OAuth. > The Custom Connections endpoint is different and the Integrations API rules do not apply to it: it has its own host, it takes no x-api-key and no authentication header of any kind, and it is called from a visitor's browser. It is identified by a workspace id and a capture key together with a reCAPTCHA token. Never tell a reader to authenticate it with an API key, and never tell them to keep its capture key out of frontend code - it is designed to live in the page. > REST error catalog keys use BRIDGE__, for example BRIDGE_CONVERSATION_0001. Some reviewed legacy handlers return a recognized code plus a symbolic suffix separated by |; preserve the complete received value and use the compatible catalog lookup on /error-codes. Custom Connections uses separate BRIDGE.CAMPAIGN_LEADS. identifiers on its own error reference. Never invent an error code or confuse the two integration surfaces. > This documentation covers the Integrations API, webhooks and Custom Connections only. It does not describe the Bridge web application or its internal APIs. > Before generating an API request, read the relevant OpenAPI specification or the individual endpoint Markdown page. llms-full.txt collects guides and endpoint descriptions; it does not embed every request and response schema. The REST and Custom Connections contracts are separate. > Preserve the published host, method, path, operationId, authentication, headers, parameter and field names, types, formats, required and nullable fields, enums, defaults, limits, and response codes. Do not invent identifiers, fields, retry rules, or delivery guarantees. When published sources conflict, identify the conflicting passages and ask Bridge support to confirm the current behavior before relying on it. > Custom Connections is the current name of the landing-page feature previously documented as Lead Capture. The existing /lead-capture documentation URLs, captureKey field, campaign-leads endpoint, and BRIDGE.CAMPAIGN_LEADS error identifiers are unchanged. This is a naming change, not a change to authentication or the API contract. > For a complete workflow, start with the task guides: /guides/first-conversation, /guides/send-attachments, /guides/send-template, /guides/agent-outbound, /guides/pagination, /guides/identifiers and /guides/responses. Read the endpoint contract as well as the recipe. Outbound requires an existing Contact, but does not require creating a separate Conversation first. > forceSend=true permits reuse of an existing active conversation; it does not create a fresh one by ignoring it and it is not idempotency. Recovery of a released recoverable conversation can occur even with false. The LeadScout and Agents outbound routes have different line-selection and controller checks; use /guides/agent-outbound. > For webhook HMAC, follow /webhooks/verifying-signatures exactly: the Python JSON serialization with sorted keys is signed; X-Bridge-Timestamp is not included in that signature. Do not claim a signed timestamp, raw-body signing, exactly-once delivery or a global event order. Use /webhooks/receive-events for durable acceptance and duplicates. > A 201 message response, 202 handoff or 202 Custom Connections response is not a provider delivery receipt. Do not invent a polling endpoint from messageId, trackingId or requestId. REST validation parsing must tolerate the compatibility difference explained in /error-codes. > The documentation is available in English (existing root URLs), Spanish (/es/) and Brazilian Portuguese (/pt-br/). Prefer the reader's language when a localized page exists, but preserve the API's exact field names, enums, routes, authentication and examples. Translations describe the same API; they do not introduce regional API hosts or behaviors. > For coding-assistant setup, use /connect-your-agent, /es/connect-your-agent or /pt-br/connect-your-agent. The Bridge documentation MCP server reads published documentation and has a separate optional feedback tool. Connecting it does not connect the coding assistant to a customer workspace or authorize live business requests. > For direct HTTP access without MCP, start at https://docs.bridge.new/llms.txt. It lists every published page in English, Spanish and Brazilian Portuguese. Choose /llms-en.json, /llms-es.json or /llms-pt-br.json for a language-specific index, and /llms-full-en.json, /llms-full-es.json or /llms-full-pt-br.json for collected content. /llms-full.txt contains the combined collection. Fetch the original OpenAPI specification for exact schemas. > For HTTP page reads, follow the .md URLs from the index or request Accept: text/markdown at the canonical page URL. The MCP virtual filesystem uses .mdx page paths instead; .mdx is not the public HTTP export extension. With Search MCP, set language to en, es or pt-BR explicitly; its default is en. > For integration capabilities and source-selection rules, read https://docs.bridge.new/skill.md. Documentation access does not authorize business API actions; use the actual user request, workspace, credentials and target identifiers for any live integration. # Actualizar conversación > Actualiza los detalles de la conversación, incluidos los participantes, el estado y el nombre. Admite actualizaciones parciales: incluye solo los campos que quieras cambiar. ## OpenAPI ````yaml /es/api-reference/openapi.yaml patch /bridge/api/v1/workspaces/{workspaceId}/conversations/{conversationId} openapi: 3.1.0 info: title: Bridge API summary: Especificación de la API de Bridge para gestionar el sistema de chat. description: >- Especificación de la API REST de integraciones de Bridge para gestionar contactos, conversaciones, mensajes, archivos, atributos personalizados, canales de proveedores, plantillas, usuarios internos y Agents. Los webhooks se documentan por separado en https://docs.bridge.new/es/webhooks; este OpenAPI contiene únicamente endpoints REST. **Arquitectura multiempresa**: las operaciones sobre recursos se limitan a un workspace específico mediante workspaceId. La comprobación de estado no incluye un workspace en su ruta. termsOfService: https://www.sainapsis.com/legal/terms-of-service contact: name: Bridge Support url: https://app.bridge.new/ email: support@sainapsis.com license: name: MIT License url: https://spdx.org/licenses/MIT.html version: 1.0.0 servers: - url: https://api-connect-us.bridge.new description: Servidor de producción security: [] paths: /bridge/api/v1/workspaces/{workspaceId}/conversations/{conversationId}: patch: tags: - Conversations API summary: Actualizar conversación description: >- Actualiza los detalles de la conversación, incluidos los participantes, el estado y el nombre. Admite actualizaciones parciales: incluye solo los campos que quieras cambiar. operationId: >- update_conversation_bridge_api_v1_workspaces__workspaceId__conversations__conversationId__patch parameters: - name: workspaceId in: path required: true schema: type: string format: uuid description: Identificador único del workspace (UUID v4). examples: - b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234 title: Workspaceid description: Identificador único del workspace (UUID v4). - name: conversationId in: path required: true schema: type: string format: uuid description: Identificador único de la conversación (UUID v4). examples: - 4e362e2b-67b2-4a7e-a9df-e9ecf9141be8 title: Conversationid description: Identificador único de la conversación (UUID v4). requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateConversation' description: >- Cuerpo de la solicitud para actualizar una conversación existente. responses: '200': description: Respuesta satisfactoria content: application/json: schema: $ref: '#/components/schemas/ConversationResponse' '403': description: Acceso prohibido content: application/json: examples: FORBIDDEN: value: title: Forbidden status: 403 code: BRIDGE_CORE_0301 schema: $ref: '#/components/schemas/Problem' '404': description: No encontrado content: application/json: examples: CONVERSATION_NOT_FOUND: value: title: Conversation Not Found status: 404 code: BRIDGE_CONVERSATION_0001 CONVERSATION_NOT_IN_WORKSPACE: value: title: Conversation Not In Workspace status: 404 code: BRIDGE_CONVERSATION_0002 WORKSPACE_NOT_FOUND: value: title: Workspace Not Found status: 404 code: BRIDGE_WORKSPACE_0001 EXTERNAL_USER_NOT_FOUND: value: title: External User Not Found status: 404 code: BRIDGE_EXTERNAL_0001 INTERNAL_USER_NOT_FOUND: value: title: Internal User Not Found status: 404 code: BRIDGE_INTERNAL_0001 schema: $ref: '#/components/schemas/Problem' '409': description: Conflicto content: application/json: examples: INTERNAL_USER_ALREADY_IN_CONVERSATION: value: title: Internal User Already In Conversation status: 409 code: BRIDGE_CONVERSATION_0101 EXTERNAL_USER_ALREADY_IN_CONVERSATION: value: title: External User Already In Conversation status: 409 code: BRIDGE_CONVERSATION_0103 INTERNAL_USER_NOT_IN_CONVERSATION: value: title: Internal User Not In Conversation status: 409 code: BRIDGE_CONVERSATION_0102 EXTERNAL_USER_NOT_IN_CONVERSATION: value: title: External User Not In Conversation status: 409 code: BRIDGE_CONVERSATION_0104 LAST_ADMIN_REMOVAL_FORBIDDEN: value: title: Last Admin Removal Forbidden status: 409 code: BRIDGE_CONVERSATION_0204 MIN_INTERNAL_USERS_REQUIRED: value: title: Min Internal Users Required status: 409 code: BRIDGE_CONVERSATION_0205 EXTERNAL_USER_NOT_IN_WORKSPACE: value: title: External User Not In Workspace status: 409 code: BRIDGE_EXTERNAL_0004 INTERNAL_USERS_NOT_IN_WORKSPACE: value: title: Internal Users Not In Workspace status: 409 code: BRIDGE_INTERNAL_0002 schema: $ref: '#/components/schemas/Problem' '422': description: Error de validación content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '429': description: Demasiadas solicitudes content: application/json: schema: $ref: '#/components/schemas/Problem' examples: WORKSPACE_BUDGET_EXHAUSTED: value: title: Too Many Requests status: 429 code: BRIDGE_RATE_LIMIT_0001 security: - x-api-key: [] components: schemas: UpdateConversation: properties: name: anyOf: - type: string - type: 'null' title: Name description: Nombre o título opcional de la conversación. examples: - Client Support - null status: anyOf: - $ref: '#/components/schemas/ConversationStatus' - type: 'null' title: Status description: >- Estado inicial de la conversación: 'active' para conversaciones visibles y 'ghost' para conversaciones invisibles hasta la primera interacción. examples: - ACTIVE participants: anyOf: - $ref: '#/components/schemas/ParticipantOperationsRequest' - type: 'null' title: Participants description: >- Operaciones para agregar y eliminar participantes de una conversación. additionalProperties: false type: object title: UpdateConversation description: Cuerpo de la solicitud para actualizar una conversación existente. ConversationResponse: properties: id: type: string title: Identifier description: Identificador único de la conversación (UUID v4). examples: - b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234 workspaceId: type: string title: Workspace Identifier description: Identificador único del workspace (UUID v4). examples: - b6cf1c4a-2b1e-4e63-8f3e-0f9d1a2a1234 participants: $ref: '#/components/schemas/ConversationParticipantsResponse' title: Participants description: Participantes de la conversación. name: anyOf: - type: string - type: 'null' title: Name description: Nombre o título opcional de la conversación. examples: - Bridge Support Team status: anyOf: - $ref: '#/components/schemas/ConversationStatus' - type: 'null' title: Status description: >- Estado actual de la conversación: 'ACTIVE' para conversaciones visibles y 'GHOST' para conversaciones invisibles hasta la primera interacción. examples: - ACTIVE createdAt: type: string format: date-time title: Created At description: Fecha y hora de creación de la conversación. examples: - '2003-04-10T09:00:00.000Z' updatedAt: type: string format: date-time title: Updated At description: Fecha y hora de la última actualización de la conversación. examples: - '2003-04-10T09:00:00.000Z' type: object required: - id - workspaceId - participants - createdAt - updatedAt title: ConversationResponse description: Cuerpo de respuesta para los detalles de una conversación. Problem: properties: title: type: string title: Title description: Resumen breve del tipo de problema. status: type: integer title: Status description: >- Código de estado HTTP generado por el servidor de origen para esta instancia del problema. detail: anyOf: - type: string - type: 'null' title: Detail description: Explicación específica de esta instancia del problema. instance: anyOf: - type: string - type: 'null' title: Instance description: Referencia URI que identifica esta instancia del problema. traceId: anyOf: - type: string - type: 'null' title: Traceid description: ID de seguimiento para depuración. code: anyOf: - type: string - type: 'null' title: Code description: >- Código para identificar el error; consulta la página de códigos de error para más detalles. errors: anyOf: - items: additionalProperties: true type: object type: array - type: 'null' title: Errors description: Lista de detalles de errores. extra: anyOf: - additionalProperties: true type: object - type: 'null' title: Extra description: Información adicional sobre el problema. type: object required: - title - status title: Problem description: Objeto que representa el cuerpo de una respuesta Problem. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ConversationStatus: type: string enum: - ACTIVE - GHOST - RELEASED - NOT_ASSIGNED_TO_HUMAN - BLOCKED title: ConversationStatus ParticipantOperationsRequest: properties: externals: anyOf: - $ref: '#/components/schemas/ExternalOperationRequest' - type: 'null' title: Externals description: >- Operaciones sobre usuarios externos; deben proporcionarse mediante las operaciones "add" y "remove". internals: anyOf: - $ref: '#/components/schemas/InternalOperationRequest' - type: 'null' title: Internals description: >- Operaciones sobre usuarios internos; deben proporcionarse mediante las operaciones "add" y "remove". type: object title: ParticipantOperationsRequest description: >- Cuerpo de la solicitud de operaciones sobre participantes al actualizar una conversación. ConversationParticipantsResponse: properties: externals: items: $ref: '#/components/schemas/ExternalParticipant' type: array title: Externals description: Lista de participantes externos. internals: items: $ref: '#/components/schemas/InternalParticipant' type: array title: Internals description: Lista de participantes internos. type: object required: - externals - internals title: ConversationParticipantsResponse description: Cuerpo de respuesta para los participantes de una conversación. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type input: title: Input ctx: type: object title: Context type: object required: - loc - msg - type title: ValidationError ExternalOperationRequest: properties: add: items: $ref: '#/components/schemas/ExternalUserIdentifierRequest' type: array title: Add description: Participantes externos que se agregarán. remove: items: $ref: '#/components/schemas/ExternalUserIdentifierRequest' type: array title: Remove description: Participantes externos que se eliminarán. type: object title: ExternalOperationRequest description: Operaciones sobre participantes externos de una conversación. InternalOperationRequest: properties: add: items: $ref: '#/components/schemas/InternalUserIdentifierRequest' type: array title: Add description: Participantes internos que se agregarán. remove: items: $ref: '#/components/schemas/InternalUserIdentifierRequest' type: array title: Remove description: Participantes internos que se eliminarán type: object title: InternalOperationRequest description: Operaciones sobre participantes internos de una conversación. ExternalParticipant: properties: identifier: type: string title: Identifier description: Valor del identificador del participante. examples: - ef7ee722-5f95-415a-9a98-81eeae178b11 identifierType: type: string enum: - ID - EMAIL - PHONE title: Identifier Type description: Tipo de identificador de participantes externos (ID, EMAIL o PHONE). examples: - EMAIL - PHONE - ID role: $ref: '#/components/schemas/UserType' title: Role description: Rol del participante en la conversación. examples: - EXTERNAL - INTERNAL joinedAt: type: string format: date-time title: Joined At description: Fecha y hora en que el participante se unió a la conversación. examples: - '2004-04-10T09:00:00.000Z' lastSeenAt: anyOf: - type: string format: date-time - type: 'null' title: Last Seen At description: Fecha y hora de la última actividad observada del participante. examples: - null - '2004-04-10T09:00:00.000Z' type: object required: - identifier - identifierType - role - joinedAt title: Participant description: Objeto que representa al participante externo de la conversación. InternalParticipant: properties: identifier: type: string title: Identifier description: Valor del identificador del participante. examples: - ef7ee722-5f95-415a-9a98-81eeae178b11 identifierType: $ref: '#/components/schemas/InternalParticipantIdentifierType' title: Identifier Type description: Tipo de identificador de participantes internos (ID o EMAIL). examples: - EMAIL - ID role: $ref: '#/components/schemas/UserType' title: Role description: Rol del participante en la conversación. examples: - EXTERNAL - INTERNAL joinedAt: type: string format: date-time title: Joined At description: Fecha y hora en que el participante se unió a la conversación. examples: - '2004-04-10T09:00:00.000Z' lastSeenAt: anyOf: - type: string format: date-time - type: 'null' title: Last Seen At description: Fecha y hora de la última actividad observada del participante. examples: - null - '2004-04-10T09:00:00.000Z' type: object required: - identifier - identifierType - role - joinedAt title: Participant description: Objeto que representa al participante interno de la conversación. ExternalUserIdentifierRequest: properties: identifier: type: string title: Identifier description: Valor del identificador del usuario. examples: - john.doe@example.com - '+13802098869' - 37673840-6259-40f9-bbe5-a7db40f8e3cf identifierType: type: string enum: - ID - EMAIL - PHONE title: Identifier Type description: Tipo de identificador de usuarios externos (ID, EMAIL o PHONE). examples: - EMAIL - PHONE - ID messageProviderType: anyOf: - $ref: '#/components/schemas/MessageProviderType' - type: 'null' title: Message Provider Type description: Tipo de proveedor de mensajería de la conversación. examples: - WHATSAPP - null providerChannelId: anyOf: - type: string - type: 'null' title: Provider Channel Identifier description: >- ID del canal del proveedor que usará Bridge para comunicarse con el usuario. brandId: anyOf: - type: string - type: 'null' title: Brand Identifier description: >- Marca propietaria de la línea corporativa utilizada para contactar al usuario. Cuando el workspace tiene al menos una línea con marca, la selección automática de líneas se limita a esta marca y la solicitud debe incluir brandId o providerChannelId; se rechaza si no incluye ninguno. Se ignora cuando el workspace no tiene líneas con marca. type: object required: - identifier - identifierType title: ExternalUserIdentifierRequest description: Cuerpo para identificar a un usuario externo en Bridge. InternalUserIdentifierRequest: properties: identifier: type: string title: Identifier description: Valor del identificador del usuario. examples: - john.doe@example.com - '+13802098869' - 37673840-6259-40f9-bbe5-a7db40f8e3cf identifierType: $ref: '#/components/schemas/InternalParticipantIdentifierType' title: Identifier Type description: Tipo de identificador de usuarios internos (ID o EMAIL). examples: - EMAIL - ID type: object required: - identifier - identifierType title: InternalUserIdentifierRequest description: Cuerpo para identificar a un usuario interno en Bridge. UserType: type: string enum: - INTERNAL - EXTERNAL - BOT title: UserType InternalParticipantIdentifierType: type: string enum: - ID - EMAIL title: InternalParticipantIdentifierType MessageProviderType: type: string enum: - WHATSAPP - SMS - TELEGRAM - INSTAGRAM - TWITTER - LINE - FACEBOOK - IMESSAGE - WHATSAPP_TEST - HEYGIA title: MessageProviderType securitySchemes: x-api-key: type: apiKey description: Copy the API key as provided by the Bridge Console. in: header name: x-api-key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.