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

# Receive an RCS test number update event

`POST receive-rcs-test-number-update-events` (webhook)

Any time you request some operation to be executed for RCS test number, that operation will be
                executed asynchronously. After operation is executed, an event is sent. Also, status of test number could be
                changed as a result of end user action (e.g. user has accepted an invitation to become a tester) and in these
                situations, 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 'TEST_NUMBER_UPDATE' event.
                Refer to [Subscriptions Management](https://www.infobip.com/docs/cpaas-x/subscriptions-management) for additional info.

## Payload

- C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsTestNumberUpdateWebhookResponse: Webhook response containing RCS test number update events
  - `results` C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsTestNumberUpdateEvent[], required: Collection of RCS test number 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 a sender for which test number is associated.
    - `testNumber` string, required: Full number in E.164 format, e.g. +1234567890. Leading '+' is optional.
    - `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.
    - `testNumberStatus` 'PENDING' | 'WAITING_FOR_TESTER_ACCEPTANCE' | 'APPROVED' | 'EXPIRED' | 'UNSUPPORTED' | 'FAILED', required: Status of the test number. It'll be updated by Infobip platform automatically and notification about test number status update will be sent to client's webhook. Following statuses are available: * `PENDING`: Test device registration is pending until 3rd party action will be executed. * `WAITING_FOR_TESTER_ACCEPTANCE`: Waiting for user to accept request to become a tester. * `APPROVED`: User has accepted to become a tester and test messages can be sent to that number. * `EXPIRED`: If user does not accept invitation within 24h, status of test number will be moved to EXPIRED. * `UNSUPPORTED`: Test number is not supported for RCS traffic. * `FAILED`: Failed mostly because of some internal service error during request processing. Please contact support.
    - `updatedAt` string, date-time, required: Timestamp when test number has been updated last time.
    - `completedAt` string, date-time: Timestamp when request has been completed. It will be null if request is still in progress.
    - `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)