POST /v1/Services/{ChatServiceSid}/Conversations/{ConversationSid}/Messages

Add a new message to the conversation in a specific service

Servers

Path parameters

Name Type Required Description
ConversationSid String Yes

The unique ID of the Conversation for this message.

ChatServiceSid String Yes

The SID of the Conversation Service the Participant resource is associated with.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/x-www-form-urlencoded"

X-Twilio-Webhook-Enabled String No

The X-Twilio-Webhook-Enabled HTTP request header

Possible values:

  • "false"
  • "true"

Request body fields

Name Type Required Description
Author String No

The channel specific identifier of the message's author. Defaults to system.

Attributes String No

A string metadata field you can use to store any data you wish. The string value must contain structurally valid JSON if specified. Note that if the attributes are not set "{}" will be returned.

ContentVariables String No

A structurally valid JSON string that contains values to resolve Rich Content template variables.

MediaSid String No

The Media SID to be attached to the new Message.

Body String No

The content of the message, can be up to 1,600 characters long.

DateUpdated String No

The date that this resource was last updated. null if the message has not been edited.

ContentSid String No

The unique ID of the multi-channel Rich Content template, required for template-generated messages. Note that if this field is set, Body and MediaSid parameters are ignored.

DateCreated String No

The date that this resource was created.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.