Managani Docs

Appearance

Create or resume an active widget chat conversation, optionally with its first message ​

When body or attachments are provided, the conversation and first visitor message are persisted transactionally. Omitting them preserves the legacy create-or-resume response.

Request preparation ​

Send a POST request to /widget/chat/conversations on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.

No separate path or query parameters are declared for this operation in the current specification. Do not invent filtering or pagination options from another endpoint; use only the contract shown here.

This operation defines an optional request body. Documented media types: application/json. Review required fields, nested objects, and allowed values in the request schema. Keep identifiers and field types intact when replacing example data with your own values.

Authentication and scope ​

The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.

Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.

Response handling ​

The documented responses for Create or resume an active widget chat conversation, optionally with its first message are:

  • 201: Created
  • 400: Message required when an initial message payload is provided
  • 401: Signed user token required

Exercise this operation with controlled test data before enabling it in an automated workflow. Validate the request against the schema and inspect the response before updating local state. Do not assume that a successful response means background processing has finished; follow any documented status or follow-up operation when the action queues additional work.

If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.

Create or resume an active widget chat conversation, optionally with its first message​

POST
/widget/chat/conversations

When body or attachments are provided, the conversation and first visitor message are persisted transactionally. Omitting them preserves the legacy create-or-resume response.

Authorizations​

BearerAuth

JWT token from login

Type
HTTP (bearer)
or
AccessToken

Personal access token. Value: Token <your-token>

Type
API Key (header: Authorization)

Request Body​

application/json
JSON
{
  
"body": "string",
  
"attachments": [
  
  
{
  
  
}
  
],
  
"page": {
  
},
  
"metadata": {
  
}
}

Responses​

Created

application/json
JSON
{
  
"conversation": "string",
  
"message": "string",
  
"ai": {
  
},
  
"fragments": "string",
  
"routing": "string"
}

Playground​

Authorization
Body

Samples​

Powered by VitePress OpenAPI