---
title: "Check RCS capability (async)"
method: POST
path: "/rcs/2/capability-check/notify"
tags: ["channels", "rcs", "rcs-capability-check"]
---

# Check RCS capability (async)

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

## 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/notify`
- 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 10,000 phone numbers in a single request. The [Capability Check result](#channels/rcs/receive-capability-check-result) returns asynchronously and provides the capability status 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

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckAsyncRequest
  - `sender` string, required: Identifier of an RCS sender that will be used to send message.
  - `phoneNumbers` string[], required: A list of phone numbers to check for RCS capability (for example, `["441134960001", "441134960002"]`).
  - `notifyUrl` string: The URL of your callback server where the RCS capability check report will be sent. The schema for this endpoint is documented at [Receive Capability Check result](#channels/rcs/receive-capability-check-result).If notifyUrl is empty, events will be sent to the URL you added via Subscription API. The event name is CapCheck.
  - `notifyContentType` 'application/json' | 'application/xml': The preferred content type for the RCS capability check report.
  - `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

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckAsyncResponse
  - `bulkId` string, required: The ID that uniquely identifies the request. This ID is automatically generated and will be included in the API response.
  - `capabilityCheckRequestStates` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62CapabilityCheckRequestState[], required: The sync response from the RCS capability checker for the specified phone numbers. Represents the current status of the requests.
    - `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.
    - `status` 'PENDING_TIME_VIOLATION' | 'DELIVERED_TO_OPERATOR' | 'PENDING_WAITING_DELIVERY' | 'UNDELIVERABLE_REJECTED_OPERATOR' | 'DELIVERED_TO_HANDSET' | 'REJECTED_NETWORK' | 'PENDING_ENROUTE' | 'REJECTED_PREFIX_MISSING' | 'UNDELIVERABLE_NOT_DELIVERED' | 'REJECTED_DND' | 'REJECTED_SOURCE' | 'REJECTED_NOT_ENOUGH_CREDITS' | 'REJECTED_SENDER' | 'REJECTED_DESTINATION' | 'EXPIRED_EXPIRED' | 'REJECTED_NOT_REACHABLE' | 'REJECTED_PREPAID_PACKAGE_EXPIRED' | 'REJECTED_DESTINATION_NOT_REGISTERED' | 'REJECTED_ROUTE_NOT_AVAILABLE' | 'REJECTED_FLOODING_FILTER' | 'REJECTED_SYSTEM_ERROR' | 'EXPIRED_UNKNOWN' | 'REJECTED_DUPLICATE_MESSAGE_ID' | 'REJECTED_INVALID_UDH' | 'REJECTED_MESSAGE_TOO_LONG' | 'REJECTED_NOT_SENT' | 'EXPIRED_DLR_UNKNOWN' | 'MO_DELIVERED' | 'UNDELIVERABLE_NOT_SENT' | 'MISSING_TO' | 'INVALID_DESTINATION_ADDRESS' | 'CONCATENATED_MESSAGE_TOO_LONG' | 'REJECTED_MONTHLY_LIMIT_REACHED' | 'REJECTED_SMPP_SESSION_CLOSED' | 'INVALID_SUBACCOUNT_NAME' | 'REJECTED_GATEWAY_DATA_TOO_LONG' | 'INVALID_COMPANY_ID' | 'REJECTED_INVALID_TRACKING_DATA' | 'REJECTED_INVALID_COUNT' | 'REJECTED_FREE_TRIAL_EXCEEDED' | 'REJECTED_SUBSCRIPTION_PLAN_NOT_ACTIVE' | 'SIM_SWAP_DETECTED' | 'DEACTIVATED_LIST' | 'INVALID_CLIENT_NETWORK' | 'CURRENCY_CHANGE_IN_PROGRESS' | 'REJECTED_UNREACHABLE_DESTINATION' | 'SIGNALS_BLOCKED' | 'VOLUMETRIC_BLOCKED' | 'REJECTED_BLOCKED_TEMPLATE' | 'REJECTED_INVALID_PLATFORM_PARAMETERS' | 'REJECTED_SHORT_DOMAIN_NOT_VERIFIED' | 'REJECTED_10DLC_LIMIT_REACHED' | 'REJECTED_INVALID_BYO_EXTERNAL_ID', required: [The status](https://www.infobip.com/docs/essentials/api-essentials/response-status-and-error-codes) of RCS capability check request for the specified phone number.

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