---
title: "Receive an RCS sender update event"
method: POST
path: "receive-rcs-sender-update-events"
tags: ["channels", "rcs", "rcs-service-management", "rcs-sender-management"]
---

# Receive an RCS sender update event

`POST receive-rcs-sender-update-events` (webhook)

Any time you request some operation to be executed for RCS sender, that operation will be
                executed asynchronously. After operation is executed, an event is sent. Also, some operations for RCS sender
                can be executed by Infobip team (e.g. launching a sender) and for these operations, an event will be sent too.
                If you would like to receive these events, you need to subscribe to this event over 'RCS' channel, and specify the
                'SENDER_UPDATE' event. Refer to [Subscriptions Management](https://www.infobip.com/docs/cpaas-x/subscriptions-management)
                for additional info.

## Payload

- C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsSenderUpdateWebhookResponse: Webhook response containing RCS sender update events
  - `results` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsSenderUpdateEvent[], required: Collection of RCS sender update events
    - `event` string, required: Event type identifier for webhook notifications. Indicates the type of status change that occurred.
    - `senderName` string, required: Unique identifier of Sender entity for RCS channel within Infobip platform.
    - `reason` 'SENDER_SUBMITTED' | 'SENDER_CREATED_OR_EDITED' | 'LAUNCH_REQUEST_SUBMITTED' | 'LAUNCH_REQUEST_RESULT' | 'NEW_PROVIDER_AVAILABLE' | 'UNKNOWN', required: Reason describing why the sender status was updated. Following reasons are available: * `SENDER_SUBMITTED`: Sender creation or update request has been submitted and is being processed. * `SENDER_CREATED_OR_EDITED`: Sender has been successfully created or edited and is available for further actions (e.g. testing). * `LAUNCH_REQUEST_SUBMITTED`: Launch request has been submitted for the sender and the launch process has started. * `LAUNCH_REQUEST_RESULT`: Sender status has been updated as a result of the launch request completing with providers (successfully, partially, or unsuccessfully). * `NEW_PROVIDER_AVAILABLE`: A new provider has become available for an already launched Sender. The sender status has transitioned to LAUNCHED_PARTIAL_SUCCESS to indicate that launch with the new provider is available. * `UNKNOWN`: Reason for the sender status update cannot be determined.
    - `senderStatus` 'DRAFT' | 'PENDING' | 'READY_FOR_TESTING' | 'PENDING_LAUNCH' | 'SENDER_UPDATE_REQUIRED' | 'LAUNCHED_IN_PROGRESS' | 'LAUNCHED_PARTIAL_SUCCESS' | 'LAUNCHED', required: Status of the sender. It'll be updated by Infobip platform automatically and notification about sender status update will be sent to client's webhook. Following statuses are available: * `DRAFT`: Status returned when the Sender is created in Draft state via the UI. * `PENDING`: Status returned while the creation or update of the Sender is being processed. * `READY_FOR_TESTING`: Status indicating that the Sender has been created, is unlocked for editing, and testing is allowed on any device. If the launch process finishes unsuccessfully (i.e., all Providers have REJECTED), the Sender reverts to this status. * `PENDING_LAUNCH`: Status indicating that a launch has been requested through the Account Manager, RR (future), or CUP UI (future). The Sender is locked and cannot be edited. * `SENDER_UPDATE_REQUIRED`: Status indicating that after PENDING_LAUNCH, an update to the Sender is required. The Sender is unlocked for editing. * `LAUNCHED_IN_PROGRESS`: Status indicating that at least one Provider has successfully COMPLETED the launch of the Sender. The Sender is locked and ready for sending traffic, but the launch process with all Providers is not yet complete. * `LAUNCHED_PARTIAL_SUCCESS`: Status indicating that all Providers have completed their launch process with mixed results — some Providers have COMPLETED successfully, and others have REJECTED. The Sender remains locked and can be used for sending traffic. * `LAUNCHED`: Status indicating that all selected Providers have successfully COMPLETED the launch of the Sender.
    - `googleAgentId` string: Google Agent ID associated with this sender. Only included during the first transition to READY_FOR_TESTING status.
    - `updatedAt` string, date-time, required: Timestamp when sender has been updated last time. (ISO 8601-style timestamp)
    - `platform` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913PlatformParameters: Platform parameters that would be associated with the sender. Please note that platform parameters must be created before they can be associated with the sender. For more details, see [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `applicationId` string: ID of the Application that would be associated with the sender.
      - `entityId` string: ID of the Entity that would be associated with the sender.

## 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)