Create a Channel

Before sending OTP messages, you need to create a WhatsApp channel for your brand. The request below helps you set up the channel and connect it with your WhatsApp Business Account.

Endpoint and Headers

POST https://verify.useinsider.com/v1/channel/create

This API key is sensitive and should never be used on the frontend or mobile SDK; it should only be implemented on the backend.

Headers

Body Parameters

Sample Request

Every request made to the request endpoint requires a request body formatted in JSON and containing your parameters. 

Below is a sample request to create a new WhatsApp verification channel.

curl --location 'https://verify.useinsider.com/v1/channel/create' \
--header 'Content-Type: application/json' \
--header 'x-ins-auth-key: 1a2b3c4d5e6f' \
--data '{
    "channel": "whatsapp"
}'

Sample Responses

201 Created

This response indicates that your request was successfully completed.

{
    "status": "success"
}

400 Bad Request

Invalid request payload:

{
    "errors": [
        {
            "message": "invalid request payload"
        }
    ]
}

Invalid channel value:

{
    "errors": [
        {
            "message": "this field must be one of these:whatsapp",
            "field": "channel"
        }
    ]
}

Channel already exists:

{
    "errors": [
        {
            "message": "channel already exists"
        }
    ]
}

401 Unauthorized

{
    "errors": [
        {
            "message": "unauthorized"
        }
    ]
}

429 Too Many Requests

{
    "errors": [
        {
            "message": "rate limit exceeded"
        }
    ]
}

500 Internal Server Error

{
    "errors": [
        {
            "message": "server error"
        }
    ]
}

Limitations

• All functions must be executed with a simple HTTPS POST request.

• The API Key should be provided as the authorization key in the request header. If the key is incorrect, the operation will not be executed, and an authorization error will be returned in the response.

• The service is subject to a rate limit of 25 requests per minute to ensure optimal system performance, and clients exceeding this limit will receive an HTTP 429 Too Many Requests response.