Channels

Get your channels

Changed on

Every market you send SMS in, your WhatsApp account, your RCS agent and the numbers you carry phone calls on — with each one's status, and what each market has supplied.

Status lives on the channel, never on you or your brand. An identity has no lifecycle; what has one is the registration of a sender in a market and the approval of a channel. So a customer live in one country and mid-registration in another reports exactly that, rather than one flattened answer.

sms[n].compliance carries what each market holds: brand and campaign for markets that register with a compliance regime such as US TEN_DLC, and documents for markets that pre-register an alphanumeric or similar sender. Absent means the market registers with nobody and nothing has been supplied. GET /v3/compliance/requirements says what a market demands of any new customer; this says what you gave it.

Send x-profile-id with an organization key to read one of your profiles' channels.

get/v3/channels

Request

  • Base URL
    https://api.sent.dm
  • URL
    https://api.sent.dm/v3/channels
  • Auth
    • API key in header x-api-key
    • or HTTP bearer

Headers

x-profile-idstring uuid

Profile UUID to scope the request to a child profile. Only organization API keys can use this header. The profile must belong to the calling organization.

Response

The channels you send on

successboolean

Indicates whether the request was successful

Example response

{
  "data": {
    "sms": [
      {
        "status": "PROVISIONING"
      }
    ],
    "whatsapp": {
      "status": "PROVISIONING"
    },
    "rcs": {
      "status": "PROVISIONING"
    }
  }
}

Changes

    • info

      added the optional property /////// to the response with the status

    • info

      added the optional property /////// to the response with the status

    • info

      endpoint added