Update a Channel

The Verify API enables you to generate, send, and verify OTP codes for the SMS channel. You can utilize this API to generate OTP codes to send via SMS as defined in the payloads. Integrating it into your own websites or apps, you can trigger it on login pages, payment pages, and more.

After you create a channel for your brand, you can edit and update it later.

Endpoint and Headers

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

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 update an existing SMS verification channel with a new brand name.

curl --location 'verify.useinsider.com/v1/channel/update' \
--header 'Content-Type: application/json' \
--header 'x-ins-auth-key: 1a2b3c4d5e6f' \
--data '{
    "channel": "sms",
    "brandName": "YourBrand"
}'

Sample Responses

202 Accepted

{
    "status": "success"
}

400 Bad Request

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

400 Bad Request

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

401 Unauthorized

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

429 Too Many Requests

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

500 Internal Server Error

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

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 rate limit is 25 requests per minute.