Skip to main content
POST
Submit regulatory number verification

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). 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, 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.

Body

application/json
country
string
required

ISO-2

email
string<email>
required
type
enum<string>
Available options:
local,
mobile,
national
end_user_type
enum<string>
Available options:
individual,
business
prefix
string
address
object
end_user_attributes
object
supporting_documents
object[]
attachments
object[]

Response

Verification case created / submitted