Single Number Capability Check
The Single Number Capability Check API allows you to check the RCS capability of a single phone number, indicating whether the device supports RCS messaging features.
Prerequisites
- After you sign up, your account will be on the trial version. You must complete the KYC to access all the features in kaleyra.io.
- Before you get started, Create an API Key. To view the API Key and the SID, see View API Key and SID.
- Before sending the RCS, you must configure the RCS channel in the Kaleyra platform. To configure the RCS channel in your account, please contact your local Kaleyra representative.
API Request to Check RCS Capability for Single Number
To check RCS capability for single number, use the https://rcs-api.<pod>.kaleyra.io/v1/<sid>/rcs/lookup/<deviceAddress> with the following request method:
The following is the request format to check RCS capability for single number:
curl --location 'https://<api_domain>/v1/<sid>/rcs/lookup/<deviceAddress>' \
--header 'Accept: <content-type>'
--header 'api-key: <api-key>'
The following is the sample request that describes how to check RCS capability for single number:
curl --location '[https://rcs-api.na.kaleyra.io/v1/XXXXX6913850XXXX/rcs/lookup/+170XXXXXXXX'\
--header 'Accept: application/json'
--header 'api-key: XXXXX3b8497f58a94e84b671aca43XXXX'URL Parameters and Headers
The following is the list of parameters and headers to send the outgoing message request:
| Parameter/Headers | Data Type | Description | Example | Mandatory? |
|---|---|---|---|---|
sid | String | Account SID (Security Identifier). | XXXXX6913850XXXX | Yes |
Content-Type | String | Indicates the format of the content the API will be processing. | The only allowed value is application/JSON | Yes |
api-key | String | API key generated from kaleyra.io account. | XXXXX3b8497f58a94e84b671aca43XXXX | Yes |
deviceaddress | String | Phone number in E.164 format (with leading "+") | +170XXXXXXXX | Yes |
Following is the list of attributes to be used in the payload to check single number capability:
| Parameter | Data Type | Description | Example | Mandatory? |
|---|---|---|---|---|
deviceAddress | Array of String | List of device addresses to look up, typically phone numbers in E.164 format (including country code, with a leading “+”). | +1XXXXXXX985 | Yes |
Sample Success Response
The following is the sample success response:
{
"code": "RCS702",
"message": "Device Lookup successful",
"data": {
"deviceAddress": "1XXXXXXXXXX",
"carrierId": "AT&T",
"carrierStatus": "ACTIVE",
"rcsEnabled": true
},
"error": {}
}
Response Fields
The following table outlines the key fields returned in the API response. Each field provides specific information about the queried device(s), including carrier details, RCS capability, and message metadata. These fields help in interpreting the results and making informed decisions for message delivery and targeting.
Response | Description | Example |
|---|---|---|
| List of device addresses to look up, typically phone numbers in E.164 format (including country code, with a leading “+”). | 1XXXXXXX985 |
| Unique id/name of the carrier associated with the mobile device (Note: carrierId is currently available only for US device lookups; this response field is not returned for EU device lookups) | "AT&T" |
| Provides status information about the carrier. For example, this may indicate that the number is inactive, and so on. Note: carrierStatus is currently available only for US device lookups; this response field is not returned for EU device lookups. Values: ACTIVE, INACTIVE, UNKNOWN | "ACTIVE" |
| Indicates whether this device is capable and enabled for receiving RCS messages | “true” |
Updated about 5 hours ago
