POST /v1/Conversations/{ConversationSid}/Messages/{Sid}
Update an existing message in the conversation
Servers
- https://conversations.twilio.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
Sid |
String | Yes |
A 34 character string that uniquely identifies this resource. |
ConversationSid |
String | Yes |
The unique ID of the Conversation for this message. |
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:
|
Request body fields
Name | Type | Required | Description |
---|---|---|---|
Author |
String | No |
The channel specific identifier of the message's author. Defaults to |
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. |
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. |
DateCreated |
String | No |
The date that this resource was created. |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.