---
title: "Check RCS capability"
method: POST
path: "/rcs/2/capability-check/query"
tags: ["channels", "rcs", "rcs-capability-check"]
---

# Check RCS capability

`POST /rcs/2/capability-check/query`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/rcs/2/capability-check/query`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Use this endpoint to verify whether the phone numbers in a given list can receive RCS messages from the specified sender. You can check up to 500 phone numbers in a single request; however, for improved efficiency, performance, and response time, we recommend using smaller batches of 1 to 10 numbers in a single request. This synchronous API is typically used for routing purposes when verifying a number’s RCS capability immediately before sending a message. This API supports up to a 100 requests per second. For bulk database cleanup, we recommend to use the asynchronous Capability Check (CapCheck) API.

The response will provide the list of capability statuses for each phone number individually. Ensure the sender is configured and launched on the mobile network/carrier that manages the phone numbers being tested for RCS capability. If the sender is not launched on the network, the capability check request will always return a negative status for the tested phone numbers.

## Request body

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckSyncRequest
  - `sender` string, required: Identifier of an RCS sender that will be used to send message.
  - `phoneNumbers` string[], required: A list of phone numbers (1 to 5) to check for RCS capability (for example, `["441134960001", "441134960002"]`).
  - `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).

## Response `200`

OK

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckSyncResponse
  - `capabilityCheckResults` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckSyncResult[], required: The result of the RCS capability check for the specified phone numbers.
    - `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).

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests
- `500`: Internal Server Error

---

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