ChatCreateRequest
Start one outbound chat with a named Chat Agent on a channel, mirroring POST /v1/calls. The agent sends the first text, composed from its instructions and these inputs, and then answers each inbound text. On sms both handles are phone numbers in E.164 form. On web, participant_handle is your own stable id for the person, and agent_handle, when given, must be the chat_agent_id.
At most one open chat is allowed per channel for each (participant_handle, agent_handle) pair, so an inbound reply always points to exactly one run; a second start to a busy pair is refused.
- chatType: string
_agent _id min length:1max length:512requiredThe Chat Agent whose approved production version runs this chat.
- participantType: string
_handle min length:1max length:512requiredThe person to chat with, as their address, such as a phone number in E.164 form.
- agentType: string
_handle min length:1max length:512nullableYour organization's address to chat from, such as one of your messaging numbers in E.164 form. Omitted, Resia picks a configured sending number for you.
- channelType: enum
The channel the chat runs on: sms texts the person's phone number, and web runs the chat in your own page through POST and GET /v1/chats/{id}/messages. email is not available yet.
valuessmswebemail - databaseType: string
_id min length:1max length:512nullableThe database for this chat. An unknown, other-organization, or unready database resolves to null.
- inputsType: nullableProperties: 1
A flat JSON object satisfying the Chat Agent's input_schema, rendered into the agent's instructions before the first text. Null runs the chat with empty inputs, which requires an input schema that accepts an empty object.
- tagsType: TagsnullableProperties: 1
Open key/value labels on this record. Set any keys and any values. Filter a list by one key and value pair. Resia never interprets a tag. Do not put names, phone numbers, or any personal, health, credential, or secret information in a tag: a tag travels in URLs when used as a filter, and URLs appear in ordinary infrastructure request logs.

