Telesign · Schema
OmniReqChannelObj
Specifies a potential channel to use when sending this message, and any other details related to use of that channel.
AuthenticationCommunicationsFraud PreventionPhone IntelligenceSMSVerificationTelecommunicationsMessagingVoiceEmail IntelligenceIdentityNumber MaskingAccount
Properties
| Name | Type | Description |
|---|---|---|
| channel | string | A potential channel you want the service to use for sending this message. The order in which channels are tried depends on the order they are defined in the request. For example, if you specify `rcs` |
| fallback_time | integer | The duration of time (in seconds) that the service should wait before it concludes that the message has failed on this channel and attempts to send on the backup channel if one is provided. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/telesign/main/json-schema/telesign-omni-req-channel-obj-schema.json",
"title": "OmniReqChannelObj",
"description": "Specifies a potential channel to use when sending this message, and any other details related to use of that channel.",
"x-generated": "2026-10-07",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/telesign-engage-api-openapi.yml#/components/schemas/OmniReqChannelObj",
"type": "object",
"properties": {
"channel": {
"type": "string",
"description": "A potential channel you want the service to use for sending this message. The order in which channels are tried depends on the order they are defined in the request. For example, if you specify `rcs` and then `sms`, the service tries RCS and then attempts to use SMS as a fallback if the RCS message fails.",
"enum": [
"rcs",
"whatsapp",
"sms",
"mms",
"viber",
"email"
]
},
"fallback_time": {
"type": "integer",
"description": "The duration of time (in seconds) that the service should wait before it concludes that the message has failed on this channel and attempts to send on the backup channel if one is provided.",
"default": 300,
"minimum": 30,
"maximum": 3600
}
},
"required": [
"channel"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/telesign-omni-req-channel-obj"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.