--- title: "Receive an RCS sender launch update event" method: POST path: "receive-rcs-sender-launch-update-events" tags: ["channels", "rcs", "rcs-service-management", "rcs-sender-management"] --- # Receive an RCS sender launch update event `POST receive-rcs-sender-launch-update-events` (webhook) When a launch request is submitted for a given RCS sender, the launch status is updated individually for each provider within the selected country. This webhook delivers real-time updates whenever the launch status changes for any provider in any country. To receive these events, you must subscribe to the RCS channel and specify the SENDER_LAUNCH_UPDATE event. For more details on managing subscriptions, please refer to the [Subscriptions Management](https://www.infobip.com/docs/cpaas-x/subscriptions-management) documentation. ## Payload - C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsSenderLaunchStatusWebhookResponse: Webhook response containing RCS sender launch status update events - `results` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsSenderLaunchStatusEvent[], required: Collection of RCS sender launch status 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. - `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. - `coverage` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913CountryCoverage[], required: Coverage information by country showing launch status for each provider. - `countryCode` string, required: Country code where the sender is being launched. - `providers` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913ProviderSenderLaunchStatus[], required: List of providers in the country and their launch status. - `name` string, required: Name of the provider. - `status` 'COMPLETED' | 'IN_PROGRESS' | 'PENDING' | 'REJECTED' | 'NOT_REQUESTED' | 'NEW', required: Launch status for this specific provider. Possible values: * `PENDING`: Status returned when the launch request has not yet been submitted to the provider. * `IN_PROGRESS`: Status returned when the launch process with the provider has started. * `COMPLETED`: Status returned when the launch process with the provider has successfully finished. * `REJECTED`: Status returned when the launch process with the provider has finished unsuccessfully. * `NOT_REQUESTED`: Status returned when the provider has been excluded from the launch process. * `NEW`: Status returned when a new provider becomes available for launch in the market. - `rejectionReason` string: Reason for rejection if the sender launch has been rejected by the provider. Present only if launch request has been created without `structuredFeedback` opt-in feature. Please check [Submit resource request](#platform/resources/resource-request/submit-resource-request) for more details. - `feedback` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913ProviderSenderLaunchFeedback[]: Detailed feedback for rejection if the sender launch has been rejected by the provider. Present only if launch request has been created with `structuredFeedback` opt-in feature. Please check [Submit resource request](#platform/resources/resource-request/submit-resource-request) for more details. - `requirementKey` string: Property of a sender for which the provider reported an issue. Present only if error refers to sender property. - `externalRequirementKey` string: Property of a sender launch request for which the provider reported an issue. Present only if error refers to sender launch request property. - `errors` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913ProviderSenderLaunchRejectionError[], required: List of errors related to given `requirementKey` / `externalRequirementKey`. For list of possible errors, please check [Get feedback errors](#platform/resources/resource-request/get-feedback-errors). - `key` string, required: Code identifying the type of error. - `reason` string, required: Reason for the error. - `details` string, required: Additional details and recommended actions for the error. - `updatedAt` string, date-time, required: Timestamp when the provider status was last updated. - `updatedAt` string, date-time, required: Timestamp when launch status 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)