Telnyx · Schema
CreateNumberBlockOrderRequest
CommunicationsCPaaSVoiceSMSIoTTelecommunicationsMessagingArtificial IntelligenceMCPVoice AIPhone NumbersInference
Properties
| Name | Type | Description |
|---|---|---|
| connection_id | string | Identifies the connection associated with this phone number. |
| created_at | string | An ISO 8901 datetime string denoting when the number order was created. |
| customer_reference | string | A customer reference string for customer look ups. |
| errors | string | Errors the reservation could happen upon |
| id | string | |
| messaging_profile_id | string | Identifies the messaging profile associated with the phone number. |
| phone_numbers_count | integer | The count of phone numbers in the number order. |
| range | integer | The phone number range included in the block. |
| record_type | string | |
| requirements_met | boolean | True if all requirements are met for every phone number, false otherwise. |
| starting_number | string | Starting phone number block |
| status | string | The status of the order. |
| updated_at | string | An ISO 8901 datetime string for when the number order was updated. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/telnyx/main/json-schema/telnyx-create-number-block-order-request-schema.json",
"title": "CreateNumberBlockOrderRequest",
"x-generated": "2026-10-08",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/telnyx-phone-number-block-orders-api-openapi.yml#/components/schemas/CreateNumberBlockOrderRequest",
"properties": {
"connection_id": {
"description": "Identifies the connection associated with this phone number.",
"type": "string"
},
"created_at": {
"description": "An ISO 8901 datetime string denoting when the number order was created.",
"format": "date-time",
"readOnly": true,
"type": "string"
},
"customer_reference": {
"description": "A customer reference string for customer look ups.",
"type": "string"
},
"errors": {
"description": "Errors the reservation could happen upon",
"readOnly": true,
"type": "string"
},
"id": {
"format": "uuid",
"readOnly": true,
"type": "string"
},
"messaging_profile_id": {
"description": "Identifies the messaging profile associated with the phone number.",
"type": "string"
},
"phone_numbers_count": {
"description": "The count of phone numbers in the number order.",
"readOnly": true,
"type": "integer"
},
"range": {
"description": "The phone number range included in the block.",
"type": "integer",
"writeOnly": true
},
"record_type": {
"readOnly": true,
"type": "string"
},
"requirements_met": {
"description": "True if all requirements are met for every phone number, false otherwise.",
"readOnly": true,
"type": "boolean"
},
"starting_number": {
"description": "Starting phone number block",
"type": "string",
"writeOnly": true
},
"status": {
"description": "The status of the order.",
"enum": [
"pending",
"success",
"failure"
],
"readOnly": true,
"type": "string"
},
"updated_at": {
"description": "An ISO 8901 datetime string for when the number order was updated.",
"format": "date-time",
"readOnly": true,
"type": "string"
}
},
"required": [
"starting_number",
"range"
],
"type": "object"
}
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/telnyx-create-number-block-order-request"
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.