Webhook

Chat Incoming Event

​

Resia sends this to a Chat Agent's inbound_input_webhook_url when a text starts a new chat on a number mapped to the agent; later texts in that chat do not send it. type is chat.incoming and chat carries the channel, the person (participant_handle), and your number (agent_handle), never the message text. Reply within 30 seconds with HTTP 200 and the InboundCallInputWebhookResponse body: {"inputs": {...}} that fits the agent's input_schema. Any other answer, or no answer, starts no chat and sends no reply, so the webhook works as an allow list. Each delivery is one row in GET /v1/request-logs.

Body·

required
application/json

The body Resia POSTs to a Chat Agent's inbound_input_webhook_url when a text starts a new chat (ENG-3775). The thin WebhookEvent base carries the shared type discriminator; this event nests InboundChatInputWebhookRequest under chat. The endpoint answers with the same InboundCallInputWebhookResponse envelope an inbound call uses.

  • chat
    Type:
    required

    The chat payload of the chat.incoming event Resia sends to a Chat Agent's inbound_input_webhook_url when a text starts a new chat: the channel and the two handles.

    It never carries the message text. The handles are named for the side each belongs to, as on every chat shape (ENG-3719), so the endpoint looks the person up exactly as it reads a chat.

    Properties: 3
  • type
    const:  
    chat.incoming

Responses

  • application/json
  • application/json
Request Example for postchat.incoming
{
  "type": "chat.incoming",
  "chat": {
    "channel": "sms",
    "participant_handle": "+14155550123",
    "agent_handle": "+14155550199"
  }
}

null

Successful Response