---
title: "Receive Capability Check result"
method: POST
path: "receive-capability-check-result"
tags: ["channels", "rcs", "rcs-capability-check"]
---

# Receive Capability Check result

`POST receive-capability-check-result` (webhook)

Receive the results requested by [Check RCS capability (async)](#channels/rcs/capability-check-rcs-destinations-notify). This callback will be invoked once per each phone number with POST method.

## Payload

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckAsyncResult
  - `capabilityCheckResult` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckResult, required
    - `bulkId` string, required: The ID that uniquely identifies the request. This ID is automatically generated and will be included in the API response.
    - `messageId` string, required: A unique message ID. This ID is automatically generated and will be included in the API response.
    - `phoneNumber` string, required: The recipient's phone number that was checked for RCS capability.
    - `code` 'ENABLED' | 'UNREACHABLE' | 'REJECTED_NETWORK' | 'REJECTED_ROUTE_NOT_AVAILABLE' | 'REQUEST_FAILED' | 'PROCESSING_ERROR' | 'INVALID_DESTINATION_ADDRESS' | 'UNKNOWN_CODE', required: The result of the RCS capability check for the specified phone number. Following codes are available: * `ENABLED`: The number can receive RCS messages from the specified sender. * `UNREACHABLE`: The number cannot receive RCS messages from the specified sender. * `REJECTED_NETWORK`: Message not sent, network not allowed. * `REJECTED_ROUTE_NOT_AVAILABLE`: Route not available for that sender. * `REQUEST_FAILED`: External problems during capability check * `PROCESSING_ERROR`: The results for the number couldn’t be processed. Please try again. * `INVALID_DESTINATION_ADDRESS`: Number provided in wrong format. * `UNKNOWN_CODE`: Unknown error. Contact with support.
  - `options` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckOptions
    - `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).

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