Access Tokens1

Addresses6

Advanced Number Orders4

AI Collections14

Anthropic Messages1

Assistants46

Audio1

Audit Logs1

Authentication Providers5

AutoRechargePreferences2

Billing1

Billing Groups5

Bot Signup4

Brands16

Bucket SSL Certificate3

Bucket Usage2

Bulk Phone Number Campaigns3

Bulk Phone Number Operations5

Bundles2

Call Commands42

Call Control Applications5

Call Information2

Call Recordings11

Campaign15

CDR Reports10

CDR Usage Reports9

Chat4

cloudfs filesystems6

Clusters5

Comments2

Conference Commands23

Connections3

Contents1

Conversation Histories1

Conversations21

Country Coverage2

Coverage1

Credential Connections6

Credentials5

CSV Downloads3

Customer Service Record4

Data Migration9

Debugging1

Decision Models1

Detail Records1

Dialogflow Integration4

DIR References3

Display Identity Records8

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 Verification3

Email Webhooks5

Embeddings8

Enterprises6

Enum1

External Connections23

Fine Tuning4

FQDN Connections7

FQDNs5

functions7

Global IPs21

Hosted Numbers9

Inexplicit Number Orders3

Infringement Claims4

Integration Secrets3

Integrations5

Inventory Level1

IP Addresses4

IP Connections5

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 Session Actions3

Meeting Session Artifacts3

Meeting Session Data4

Meeting Sessions5

Memory4

Messages11

Messaging15

Messaging URL Domains1

Missions41

Mobile Network Operators1

Mobile Number Settings2

Mobile Phone Numbers3

Mobile Voice Connections5

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

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

Reputation17

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

sql databases5

Stored Payment Transactions1

Telco Data Usage Reports8

Terms of Service6

TeXML Applications5

TeXML REST Commands35

Text To Speech Commands3

Traffic Policy Profiles12

UAC Connections6

Usage Reports (BETA)2

User Bundles6

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 Numbers32

WireGuard Interfaces10

Wireless Blocklists6

Wireless Regions1

x402 Payment Transactions4

Webhooks

Callbacks91

Meeting Session Webhooks5

Regulatory Requirements

Retrieve regulatory requirements

Returns regulatory requirements for number ordering, porting, or other supported actions. Results can be filtered by phone number, requirement group, country, number type, and action.

get/regulatory_requirements

Query parameters

phone_numberstring

Phone number to check requirements for

requirement_group_idstring

ID of requirement group to check requirements for

country_codestring

Country code(iso2) to check requirements for

phone_number_type'local' | 'toll_free' | 'mobile' | 'national' | 'shared_cost'

Phone number type to check requirements for

action'ordering' | 'porting' | 'action'

Action to check requirements for

Consolidated filter parameter (deepObject style). Originally: filter[phone_number], filter[requirement_group_id], filter[country_code], filter[phone_number_type], filter[action]

{
  "phone_number": "+41215470622",
  "requirement_group_id": "d4c0b4a6-7bd2-40c5-a3b9-2acd99e212b2",
  "country_code": "DE"
}

Response

An array of Regulatory Requirements Responses

Example response

{
  "data": [
    {
      "country_code": "DE",
      "phone_number_type": "local",
      "action": "ordering",
      "regulatory_requirements": [
        {
          "description": "Address matching the DID area code (street, building number, postal code, city and country)",
          "id": "12ade33a-21c0-473b-b055-b3c836e1c292",
          "example": "600 Congress Avenue, 14th Floor, Austin, TX 78701",
          "name": "Address matching the DID area code",
          "field_type": "address_id",
          "acceptance_criteria": {
            "locality_limit": "Identical locality as the numbers desired",
            "time_limit": "Less than 5 months old",
            "regex": "regex field value must match",
            "case_sensitive": "Whether field value is case sensitive",
            "acceptable_characters": "Characters that can be included in field value",
            "max_length": "10",
            "min_length": "5"
          }
        }
      ]
    }
  ]
}

Changes

Changed in 3 of the 99 revisions of this API.251025

Sep 16, 2026a6a61a29ecdd5510See the full diff
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 17, 20261571b0380bd7155See the full diff
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the response property // became optional for the status
  response-property-became-optional
- ▲
  the // response's property type changed from integer to string, and format from int32 to no format for status
  response-property-type-changed
- ▲
  the // response's property type changed from integer to string, and format from int32 to no format for status
  response-property-type-changed
- ▲
  the // response's property type changed from integer to string, and format from int32 to no format for status
  response-property-type-changed
- ▲
  the // response's property type changed from integer to string, and format from int32 to no format for status
  response-property-type-changed
- ▲
  the // response's property type changed from integer to string, and format from int32 to no format for status
  response-property-type-changed
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 4, 20268f5f4e5379945510See the full diff
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ▲
  the // response's property type changed from string to integer, and format from no format to int32 for status
  response-property-type-changed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
- ○
  the response property // became required for the status
  response-property-became-required
This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 99 revisions, 1 has no diff computed.

Full history