Capability

A capability query checks the options available for reaching the contact on the channels on which it has a channel identity.

Capability queries can only be executed for contacts that already exist in a project and app. For executing the request, either the contact ID or the channel recipient identities of the contact are required.

The request is executed asynchronously, therefore the service responds immediately. The result of the capability query is sent to the registered webhook for the CAPABILITY trigger.

Capability lookup

This method is asynchronous - it immediately returns the requested Capability registration. Capability check is then delivered as a callback to registered webhooks with trigger CAPABILITY for every reachable channel.

SecurityBasic or oAuth2
Request
path Parameters
project_id
required
string

The unique ID of the project. You can find this on the Sinch Dashboard.

Request Body schema: application/json
required

The query capability request.

app_id
required
string

The ID of the app to use for capability lookup.

required
Contact ID (object) or Channel Identities (object) (Recipient)

Identifies the recipient.

request_id
string

ID for the asynchronous response, will be generated if not set. Currently this field is not used for idempotency.

Responses
200

A successful response.

Response Schema: application/json
app_id
string

The ID of the app to use for capability lookup.

Contact ID (object) or Channel Identities (object) (Recipient)

Identifies the recipient.

request_id
string

ID for the asynchronous response, will be generated if not set.

400

Malformed request. See common error responses for more information.

401

Incorrect credentials. See common error responses for more information.

403

Correct credentials but you don't have access to the requested resource. See common error responses for more information.

500

Correct credentials but you don't have access to the requested resource. See common error responses for more information.

501

Something went wrong on our end, try again with exponential back-off. See common error responses for more information.

post/v1/projects/{project_id}/capability:query
Request samples
application/json
{
  • "app_id": "{APP_ID}",
  • "recipient": { }
}
Response samples
application/json
{
  • "app_id": "string",
  • "recipient": {
    • "contact_id": "{CONTACT_ID}"
    },
  • "request_id": "string"
}