Use the Conversation Data API to update the content of existing conversation entries instead of deleting and recreating them. With this endpoint, you can correct a message's text without deleting and recreating the entry, update the payload for non-text entries, such as attachments, and associate or update related records on an entry after it's created.
Where: This change applies to orgs with Enhanced Messaging and the Conversation Data API
enabled. Edition availability matches the existing GET /conversation-entries
endpoint.
How: To call this endpoint, you need the same access as other Conversation Data API endpoints: an External Client App configured with an Execution User who has the API Only User permission.
To update entries, send a PATCH request to /conversation-entries with
the conversationIdentifier query parameter, and include the entries to update in
the request body. Use messageText for entries with a Text format type, or
abstractMessagePayload for other format types. Each entry is processed
independently, and the response's isSuccess field, along with each entry's
success value, tells you whether the update succeeded. This endpoint shares its rate limit with
GET/conversation-entries: 90 requests per user per minute.