Access Tokens2

Actions2

Addresses6

Advanced Number Orders4

Agent Gateway APIs4

Agent Gateway Guardrails4

Agent Gateway Keys4

Agent Gateway MCP Servers4

Agent Gateway Policies5

Agent Gateway Policy Attachments3

Agent Gateway Spend Logs1

Agent Gateway Teams4

Agent Gateway Tool Permissions4

Agent Gateways5

AI Collections14

AI Gateway14

AI Tests34

Anthropic Messages1

Artifacts2

Assistants50

Audio1

Audit Logs1

Authentication Providers5

AutoRechargePreferences2

Avatars4

Billing1

Billing Groups5

Bot Signup4

Brands16

Browser Sessions4

Bucket SSL Certificate3

Bucket Usage2

Bulk Phone Number Campaigns3

Bulk Phone Number Operations5

Bundles2

Call Commands42

Call Control Applications5

Call Information3

Call Recordings11

Campaign15

CDR Reports10

CDR Usage Reports9

Chat4

cloudfs filesystems6

Clusters5

Comments2

Conference Commands23

Connections3

Contents1

Conversation Histories1

Conversations22

Country Coverage2

Coverage1

Credential Connections6

Credentials5

CSV Downloads3

Customer Service Record4

Data Migration9

Debugging1

Decision Models1

Dedicated IPs9

Detail Records1

Dialogflow Integration4

DIR References3

Display Identity Records10

Documents8

Dynamic Emergency Addresses4

Dynamic Emergency Endpoints4

Email Domain DNS Records2

Email Domains7

Email Drafts8

Email Events2

Email Inboxes19

Email Messages11

Email Suppression Imports2

Email Suppressions6

Email Templates7

Email Threads2

Email Unsubscribe Groups8

Email Validations3

Email Verification5

Email Webhooks5

Embeddings8

Enterprises6

Enum1

External Connections23

Fine Tuning4

FQDN Connections7

FQDNs5

functions8

Global IPs21

Hosted Numbers9

Inexplicit Number Orders3

Infringement Claims4

Integration Secrets3

Integrations5

Inventory Level1

IP Addresses4

IP Connections5

IP Pools7

IP Ranges3

IPs5

kv keys4

kv namespaces4

Machine Payments1

Managed Accounts8

MCP Servers5

MDR Detail Reports1

MDR Detailed Reports8

MDR Usage Reports13

Media Storage API6

Meeting Calendar Connections8

Meeting Session Actions3

Meeting Session Artifacts3

Meeting Session Data4

Meeting Sessions5

Memory5

Messages11

Messaging15

Messaging URL Domains1

Missions41

Mobile Network Operators1

Mobile Number Settings2

Mobile Phone Numbers3

Mobile Voice Connections5

Namespaces3

Network Routes4

Networks9

Noise Suppression Engines1

Notifications16

Number Lookup1

Number Portout14

Number Settings7

numbers features1

OAuth Clients10

OAuth Discovery2

OAuth Grants6

OAuth Protocol7

OpenAI Chat3

OpenAI Embeddings2

Operations1

Opt-Out Management6

Organization Users4

OTA updates2

Outbound Voice Profiles5

Pay Connectors5

Phone Number Batches2

Phone Number Block Orders3

Phone Number Blocks Background Jobs3

Phone Number Campaigns5

Phone Number Configurations11

Phone Number Orders21

Phone Number Porting1

Phone Number Reservations4

Phone Number Search2

Phone Numbers3

Porting Orders53

Presigned Object URLs1

Pricing2

Private Wireless Gateways4

Profiles11

Programmable Fax Applications5

Programmable Fax Commands6

Pronunciation Dictionaries5

Public Internet Gateways4

Push Credentials4

Queue Commands9

RCS9

RCS Agents10

RCS Brands5

Reference Data3

Regions1

Regulatory Requirements3

Reporting8

Reports2

Reputation22

Requirement Groups10

Requirement Types2

Requirements4

Research2

Room Compositions4

Room Participants2

Room Recordings4

Room Sessions7

Rooms6

Rooms Client Tokens2

Session Analysis3

SETI Observability1

Settings2

Shared Campaigns5

Short Codes3

SIM Card Actions4

SIM Card Group Actions2

SIM Card Groups9

SIM Card Orders4

SIM Cards26

SIPREC Connectors4

Sources3

Speech to Text Batch Reports8

Speech To Text Capabilities1

Speech To Text over WebSockets1

Speech to text Usage Reports2

Spend Limits4

sql databases5

stateful actors1

Stored Payment Transactions1

Tailscale Subnet Routers5

Telco Data Usage Reports8

Terms of Service6

TeXML Applications5

TeXML REST Commands35

Text To Speech Commands3

Traffic Policy Profiles12

Tunnels5

UAC Connections7

Usage Reports (BETA)2

User Bundles6

User Profile2

User Tags1

UserAddresses6

Verification Requests7

Verified Numbers5

Verify16

Virtual Cross Connects7

Voice Channels6

Voice Clones6

Voice Designs7

Voice SDK Stats2

Voicemail3

WDR Detail Reports1

Web Search1

Webhooks2

Whatsapp Business Accounts14

Whatsapp Message Templates10

Whatsapp messaging1

Whatsapp Phone Numbers34

Whatsapp Signup5

WireGuard Interfaces10

Wireless Blocklists6

Wireless Regions1

x402 Payment Transactions4

Webhooks

Callbacks97

Meeting Session Webhooks6

Phone Numbers3

Hosted Numbers

Changes to Check hosted messaging eligibility

post/messaging_hosted_number_orders/eligibility_numbers_check

Feb 20, 20265d53041d4ddd Revision changes
- breaking
  the response's property format changed from integer to no format for status
- breaking
  the response's property format changed from integer to no format for status
- info
  the / request property format was generalized from +E.164 to no format
Feb 4, 2026a3a64a14ed68 Revision changes
- info
  api tag Hosted Numbers added
- info
  api tag Messaging Hosted Number removed
Feb 3, 20266a9394d3d3bb Revision changes
- info
  api tag Messaging Hosted Number added
- info
  api tag Hosted Numbers removed
Dec 15, 202515a388e2af97 Revision changes
- info
  api tag Hosted Numbers added
- info
  api tag Messaging Hosted Number removed
Aug 15, 2025c57f4613ea87 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
Aug 11, 20250606a8c47df7 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 11, 20255e703a375518 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 11, 202545a854866005 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 8, 20252e72aa01a5a1 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 8, 20257952080be8f8 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 8, 2025144abaf03f62 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 8, 202510aa5bc09ecc Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 7, 2025d7484a0a7768 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 7, 20258e5f0d46ddd6 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 7, 2025676a368c011d Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 5, 2025f618a1006b1a Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 5, 202551b123d64141 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 4, 20255ea2f9679014 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 4, 2025b027d7073c5b Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 4, 202544161174fc15 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
Aug 4, 2025d0bb8be24d5a Revision changes
- breaking
  the / response's property format changed from json-pointer to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
Aug 4, 2025f60b6a1dffb2 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 4, 2025441e11d27bba Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
Aug 4, 2025ddc1a62684d2 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 4, 2025ae0258dceac3 Revision changes
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the response's property type changed from integer to string, and format from int32 to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
Aug 4, 20259092c0625f49 Revision changes
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
- breaking
  the response's property type changed from string to integer, and format from no format to int32 for status
Aug 4, 2025b9a59c2da231 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property format changed from int to no format for status
- breaking
  the response's property format changed from int to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
- breaking
  the / response's property format changed from json-pointer to no format for status
Aug 1, 20259922dcb29641 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Aug 1, 2025f87271113641 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Aug 1, 202561d945742de3 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Aug 1, 202599020e181f1c Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Aug 1, 20253614a68dc607 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 31, 202547ead24182c8 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 30, 202513eaae046af7 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 25, 2025b7607afaef95 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 25, 2025dd0dfcd94701 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 24, 20256ad7361a2335 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 24, 2025253d9a1bba97 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 23, 20251083e5c24d8f Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 16, 2025b5433e9b6e42 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 15, 202534fed4d6b28d Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 15, 202567c9fa18d5ef Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 15, 202599b0d0af53c6 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 10, 202598029c9ccdd5 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 8, 20251059b083160b Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 8, 2025d49a13e1ec17 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 7, 2025657402475201 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 7, 2025d671264e7ab5 Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
Jul 3, 202518c5992ca257 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
- breaking
  the response's property type changed from string to integer, and format from int to int32 for status
Jul 2, 2025b443330a00cd Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status
- breaking
  the response's property type changed from integer to string, and format from int32 to int for status

Show earlier changes