--- title: "Receive RCS delivery reports" method: POST path: "receive-outbound-rcs-message-delivery-reports" tags: ["channels", "rcs", "rcs-logs-and-status-reports"] --- # Receive RCS delivery reports `POST receive-outbound-rcs-message-delivery-reports` (webhook) For each message that you send out, we can send you a delivery report. For this to work you need to have an endpoint to forward the reports to. Please specify the endpoint per each message via the `webhooks > delivery > url` parameter. Alternatively, you can provide the endpoint’s URL to Customer support and they will set it up for you. Contact support@infobip.com if you require help. ## Payload - B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsWebhookDeliveryReports - `results` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsWebhookDeliveryReport[]: Collection of reports, one per every message. - `bulkId` string: Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request. - `channel` 'RCS' | 'SMS' | 'MMS': The channel used to deliver a message. This property will be present only if the original message was sent with the failover option defined. The property will be included in the delivery report for the original RCS message and for the failover message (in case the failover was triggered). - `price` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsDlrMessagePrice: Price object with traffic type information. - `trafficType` 'BASIC' | 'SINGLE' | 'RICH' | 'RICH_MEDIA' | 'P2A_CONVERSATION' | 'P2A_INTERACTIVE_SESSION': Traffic type applied to the RCS message that the delivery report refers to. Null for not chargeable RCS messages. - `pricePerMessage` number: Price per one message. - `currency` string: The currency in which the price is expressed. - `status` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62MessageStatus: Indicates the [status](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) of the message and how to recover from an error should there be any. - `groupId` integer: Status group ID. - `groupName` 'ACCEPTED' | 'PENDING' | 'UNDELIVERABLE' | 'DELIVERED' | 'EXPIRED' | 'REJECTED': Status group name that describes which category the status code belongs to, i.e., [PENDING](https://www.infobip.com/docs/essentials/response-status-and-error-codes#pending-general-status-codes), [UNDELIVERABLE](https://www.infobip.com/docs/essentials/response-status-and-error-codes#undeliverable-general-status-codes), [DELIVERED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#delivered-general-status-codes), [EXPIRED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#expired-general-status-codes), [REJECTED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#rejected-general-status-codes). - `id` integer: Status code ID. - `name` string: [Status code](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) name. - `description` string: Human-readable description of the status. - `action` string: Action to take to recover from the error. - `error` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62MessageError: Indicates whether an [error](https://www.infobip.com/docs/essentials/response-status-and-error-codes#error-codes) occurred during the query execution. - `groupId` integer: Error group ID. - `groupName` 'OK' | 'HANDSET_ERRORS' | 'USER_ERRORS' | 'OPERATOR_ERRORS': Error group name that describes which category the error code belongs to. - `id` integer: Error ID. - `name` string: [Error name](https://www.infobip.com/docs/essentials/response-status-and-error-codes#error-codes). - `description` string: Human-readable description of the error. - `permanent` boolean: Indicates whether the error is recoverable or not. - `conversation` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationInfo: Conversation information associated with the message. - `canInitiate` boolean, required: Indicates whether this message can initiate or trigger a conversation. If the message already belongs to a conversation, the value is false. - `id` string: Unique conversation identifier. Present when the message belongs to a conversation, null otherwise. - `messageId` string: Unique message ID. - `doneAt` string, date-time: Date and time when the Infobip services finished processing the message (i.e., delivered to the destination, network, etc.). Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ. - `interactionType` 'BASIC_MESSAGE' | 'SINGLE_MESSAGE' | 'RICH_MESSAGE' | 'RICH_MEDIA_MESSAGE': The interaction type of the message that was sent. Note: this describes the message structure, not the billing category, which may differ. - `messageCount` integer: The number of sent messages. - `sentAt` string, date-time: Date and time when the message was sent. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ. - `mccMnc` string: Mobile country and network codes. - `callbackData` string: Callback data sent through ‛callbackData‛ field when sending message. - `to` string: Message destination address. - `sender` string: The sender ID which can be alphanumeric or numeric (e.g., `CompanyName`). - `platform` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62Platform: Platform options. For more details, see [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). - `entityId` string: Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). - `applicationId` string: Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). - `campaignReferenceId` string: ID of a campaign that was sent in the message. ## Acknowledgement `200` Your server returns this code if it accepts the callback. --- [API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)