How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Telnyx Verification Requests API

Manage your tollfree verification requests

Telnyx Verification Requests API is one of 169 APIs that Telnyx publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Verification Requests. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.telnyx.com/v2.

6 operations 3 paths 14 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.telnyx.com/v2
Authentication
HTTP Bearer, HTTP Bearer, OAuth 2.0, HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 6

Telnyx Verification Requests API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP bearer tokens (branded-calling_bearerAuth). It supports OAuth 2.0 (oauthClientAuth) using the authorizationCode and clientCredentials flows, exposing 1 scope. It accepts HTTP bearer tokens (JWT) (outbound-voice-profiles_bearerAuth). It accepts HTTP bearer tokens (pronunciation-dicts_bearerAuth). It accepts HTTP bearer tokens (JWT) (stored-payment-transactions_bearerAuth). By default, every request must be authenticated.

  • branded-calling_bearerAuth — API key passed as a Bearer token in the Authorization header
  • oauthClientAuth — OAuth 2.0 authentication for Telnyx API and MCP integrations
  • pronunciation-dicts_bearerAuth — Telnyx API v2 key. Obtain from https://portal.telnyx.com

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Verification Requests 6

Manage your tollfree verification requests

GET
/messaging_tollfree/verification/requests
List Verification Requests
ListVerificationRequests 7 params → 2004XX
POST
/messaging_tollfree/verification/requests
Submit Verification Request
SubmitVerificationRequest body → 2004XX
DELETE
/messaging_tollfree/verification/requests/{id}
Delete Verification Request
DeleteVerificationRequest 1 param → 2004044XX
GET
/messaging_tollfree/verification/requests/{id}
Get Verification Request
GetVerificationRequest 1 param → 2004XX
PATCH
/messaging_tollfree/verification/requests/{id}
Update Verification Request
UpdateVerificationRequest 1 param body → 2004XX
GET
/messaging_tollfree/verification/requests/{id}/status_history
Get Verification Request Status History
GetVerificationStatusHistory 3 params → 2004XX

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are VerificationRequestStatus (38 properties), VerificationRequestEgress (36 properties), TFVerificationRequest (33 properties), toll-free-verification_Error (5 properties). Each schema is shown below with its type and property counts.

toll-free-verification_EntityType
string
Business entity classification
Paginated_VerificationRequestStatus_
object
A paginated response
2 properties 2 required
toll-free-verification_Error
object
5 properties 2 required
Paginated_VerificationStatusHistoryEntry_
object
A paginated response
2 properties 2 required
TFVerificationStatus
string
Tollfree verification status
UseCaseCategories
string
Tollfree usecase categories
VerificationRequestStatus
object
A verification request and its status, suitable for returning to users
38 properties 20 required
toll-free-verification_Errors
object
1 property
Volume
string
Message Volume Enums
TFPhoneNumber
object
A phone number
1 property 1 required
Url
object
1 property 1 required
VerificationRequestEgress
object
A verification request as it comes out of the database
36 properties 20 required
TFVerificationRequest
object
The body of a tollfree verification request
33 properties 18 required
VerificationStatusHistoryEntry
object
A single entry in the verification request status history
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telnyx-verification-requests-api-openapi.yml Raw ↑

Other APIs Telnyx publishes across the network.

Telnyx Access Tokens API
Telnyx Addresses API
Telnyx Advanced Number Orders API
Telnyx Assistants API
Telnyx Audio API
Telnyx Audit Logs API
Telnyx Authentication Providers API
Telnyx AutoRechargePreferences API
Telnyx Billing API
Telnyx Billing Groups API
Telnyx Brands API
Telnyx Bucket SSL Certificate API
Where this information came from

This is an independent, third-party profile of Telnyx Verification Requests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.