Overview

Programmatically manage sender IDs, OTP templates, allow lists, and block lists for the Verify API.

The Management API lets you configure account-level Verify settings without going through the Prelude dashboard. It covers three resource families:

Sender IDs

Branded identifiers that appear as the sender of verification messages. Submit new sender IDs for approval and list the ones currently registered on your account.

Phone number lists

Allow list entries bypass anti-fraud checks; block list entries reject verifications. Use these endpoints to script bulk updates or sync lists from your own fraud tooling.

OTP templates

The branding and delivery settings a verification is sent with. Create one template per sub-customer so each gets its own suffix, code size and rate limits.

Access to the Management API is opt-in. Contact our support team to enable it on your account.

Sender ID endpoints

• List available sender IDs: GET /v2/verification/management/sender-id
• Submit a sender ID: POST /v2/verification/management/sender-id

Template endpoints

• List OTP templates: GET /v2/verification/management/templates
• Create an OTP template: POST /v2/verification/management/templates
• Retrieve an OTP template: GET /v2/verification/management/templates/{template_id}
• Update an OTP template: PATCH /v2/verification/management/templates/{template_id}
• Delete an OTP template: DELETE /v2/verification/management/templates/{template_id}

An update is a partial update: a field you omit keeps its stored value.

Phone number endpoints

All three endpoints take an {action} path parameter that must be either allow or block.

• Get phone numbers: GET /v2/verification/management/phone-numbers/{action}
• Add a phone number: POST /v2/verification/management/phone-numbers/{action}
• Delete a phone number: DELETE /v2/verification/management/phone-numbers/{action}

Add and delete operations are idempotent, repeating the same call will not create duplicates or return errors.