Authenticate Telesign REST API requests using HTTP Basic Auth with your Customer ID and API key (YOUR_CUSTOMER_ID:YOUR_API_KEY).
For phone number verification (OTP), call the Telesign SMS Verify or Voice Verify endpoint by POST-ing the phone number and a message template; Telesign returns a reference ID.
Collect the OTP from the user and submit it to the Telesign verification check endpoint along with the reference ID to confirm the code is valid.
For phone intelligence (fraud risk assessment without OTP), call the Telesign PhoneID endpoint with the phone number to receive risk score, phone type (mobile, landline, VOIP), and carrier information.
Parse the PhoneID response's risk object for a score and recommendation field ('allow', 'flag', 'block') to feed into your onboarding risk decision.
Store the reference ID and risk signals for audit; use the phone type data to decide whether to permit VOIP numbers in your registration flow.
Known gotchas
Telesign's product line includes both OTP delivery products and passive phone intelligence products; ensure you are calling the correct endpoint for your use case.
VOIP numbers are frequently associated with fraud; decide explicitly whether your policy allows VOIP registrations before deploying.
International phone numbers require country-appropriate message templates; test OTP delivery in target markets before launch.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp