Skip to main content
GET
Get number verification requirements

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, billing:write, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Query Parameters

country
string
required

ISO-2 country code, for example DE.

Required string length: 2
type
enum<string>
default:local
Available options:
local,
mobile,
national
end_user_type
enum<string>
default:business
Available options:
business,
individual

Response

Current verification requirements

data
object