An Operation represents a request that creates more than one resource, such as sending a message to multiple recipients. When you submit the request, the Communications API validates the input and returns an HTTP 202 Accepted response that includes an operationId header. Use the operationId value to monitor the status and progress of the Operation.
As the Operation is processed, it generates a Message with an associated messageId (different from a typical message SID) for each recipient. Each Message then creates at least one SM/MM message SID, one for each channel that we attempt.
You can associate every delivery attempt (each try to send a message to a recipient over a specific channel) with its parent Message and Operation resource by using the messageId and operationId values included in each status callback event.
You can make a GET request with the Operation ID to retrieve its status.
Sample response:
See the Message Operation API reference.
You can also use the List Message endpoint to retrieve the Message resources that an Operation created.
Sample response:
For more details, see the List Messages API reference.
See the Personalization guide to learn how to personalize messages for each recipient.