Skip to main content
Telnyx toll-free verification now supports Business Registration Number (BRN) fields to strengthen business verification and compliance. Starting February 17th, 2026, three BRN fields will be required for all new toll-free verification submissions.
The following fields are required for all new toll-free verification requests:
  • businessRegistrationNumber
  • businessRegistrationType
  • businessRegistrationCountry
Submissions missing these fields will be rejected.

Why This Matters

U.S. wireless carriers require toll-free numbers (800, 888, 877, 866, 855, 844, 833) used for SMS/MMS to complete verification. The new BRN fields provide carriers with verified business identity information, helping to:
  • Reduce verification processing time
  • Improve approval rates
  • Ensure compliance with carrier policies
  • Prevent fraudulent messaging

New Business Registration Fields

Required Fields (February 17th, 2026)

businessRegistrationNumber

The official government-issued business registration identifier. Examples by Country: Where to Find:
  • US: IRS EIN Lookup - Check your EIN confirmation letter or SS-4 form
  • Canada: CRA Business Number from your registration documents
  • UK: Companies House registration certificate
  • Australia: ABN Lookup
  • EU: VAT registration certificate from your national tax authority

businessRegistrationType

The type or classification of your business registration. Common Values:
  • EIN - U.S. Employer Identification Number
  • CRA - Canadian Revenue Agency Business Number
  • Companies House - UK company registration
  • ABN - Australian Business Number
  • VAT - European Union VAT registration
  • SSN - For U.S. sole proprietors without EIN

businessRegistrationCountry

ISO 3166-1 alpha-2 country code of the authority that issued the registration. Validation:
  • Must be exactly 2 letters
  • Only alphabetic characters (A-Z)
  • Automatically converted to uppercase ("us""US")
  • Returns HTTP 400 if invalid
Example Values: US, CA, GB, AU, DE, FR, JP See complete list: ISO 3166-1 country codes

Optional Fields

These fields are optional but recommended for faster verification processing.

doingBusinessAs

DBA, trade name, or brand name if different from your legal business name. Example: Legal name “Acme Corporation Inc.”, DBA “Acme Services”

entityType

Legal business entity classification. Value Descriptions:

optInConfirmationResponse

Message sent to subscribers confirming their opt-in. Example: "You are now subscribed to Acme alerts. Reply STOP to unsubscribe. Msg&data rates may apply."

helpMessageResponse

Automated response when subscribers text HELP. Example: "Acme Support: Call 1-800-555-0123 or email help@acme.com. Reply STOP to unsubscribe."

privacyPolicyURL

URL to your business privacy policy. Example: "https://www.acme.com/privacy"

termsAndConditionURL

URL to your business terms and conditions. Example: "https://www.acme.com/terms"

ageGatedContent

Indicates if messaging content requires age verification (18+ or 21+). Set to true for alcohol, tobacco, cannabis, or other age-restricted content.

optInKeywords

Keywords subscribers use to opt-in to your messaging program. Example: "START, YES, SUBSCRIBE, JOIN"

API Usage

Create Verification Request with BRN Fields

Endpoint: POST /public/api/v2/requests Request with BRN Fields:
Response (HTTP 201):

Retrieve Verification with BRN Fields

Endpoint: GET /public/api/v2/requests/{id}
Response (HTTP 200):

Update BRN Fields

Endpoint: PATCH /public/api/v2/requests/{id}

Code Examples

Python

JavaScript/TypeScript

Error Handling

Validation Errors (HTTP 400)

Missing Required Fields (After February 2026)

Response:

Invalid Country Code

Invalid Entity Type

Other Status Codes

Migration Guide

Timeline

Preparation Steps

1. Gather Business Registration Information Locate your:
  • Business registration number (EIN, VAT, ABN, etc.)
  • Registration type identifier
  • Issuing country code
2. Update Your Integration Add BRN fields to your API requests:
3. Test Your Implementation
  • Submit test requests with BRN fields
  • Verify fields are returned in responses
  • Test validation error handling
  • Confirm country code uppercase conversion
4. Update Error Handling Prepare for validation errors after February 2026:

Backward Compatibility

Until February 17, 2026:
  • Requests without BRN fields continue to work
  • No breaking changes to existing integrations
  • BRN fields default to null if not provided
After February 17, 2026:
  • Requests without 3 required BRN fields will be rejected (HTTP 400)
  • Update your integration before this date

Frequently Asked Questions

When do BRN fields become mandatory?

February 17th, 2026. All new verification requests must include businessRegistrationNumber, businessRegistrationType, and businessRegistrationCountry.

Do I need to resubmit existing verifications?

No. Approved verifications before February 2026 remain valid.

Where do I find my business registration number?

  • US: IRS EIN confirmation letter or IRS.gov
  • Canada: CRA Business Number registration documents
  • UK: Companies House certificate
  • Australia: ABN Lookup
  • EU: VAT registration certificate

What if I’m a sole proprietor without an EIN?

U.S. sole proprietors can use their Social Security Number as businessRegistrationNumber with type SSN. Other countries may have similar individual tax identifiers.

Can I update BRN fields after submission?

Yes. Use PATCH /public/api/v2/requests/{id} to update BRN fields.

Why are country codes converted to uppercase?

For consistency. Sending "us" automatically becomes "US" in responses and storage.

Which entity type should I choose?

Choose the type matching your official business registration:
  • SOLE_PROPRIETOR - Individual or sole proprietorship
  • PRIVATE_PROFIT - Private corporation (most common)
  • PUBLIC_PROFIT - Publicly traded company
  • NON_PROFIT - 501(c) or charitable organization
  • GOVERNMENT - Government entity

How long does toll-free verification take?

Verification typically takes 1-2 weeks, depending on the carrier review queue and the completeness of your submission. Including accurate BRN fields can speed up the process.

What happens if my verification is rejected?

You’ll receive a webhook notification with the rejection reason. Common causes:
  • Incomplete or inaccurate business information
  • Message samples don’t match your declared use case
  • Missing opt-out language in sample messages
  • Business couldn’t be verified with the provided registration number
Fix the issues and resubmit — there’s no limit on resubmissions.

Can I send messages before verification is complete?

Unverified toll-free numbers have limited throughput and may experience carrier filtering. Complete verification to unlock full sending capabilities (up to 20 MPS).

What’s the difference between toll-free verification and 10DLC registration?

Toll-Free Verification API

API reference for managing toll-free verification requests.

Messaging API

Send messages from your verified toll-free numbers.

10DLC Registration

Alternative registration path for local 10-digit numbers.

Advanced Opt-In/Out

Configure opt-in/out behavior including toll-free specific handling.

Support

Need help with toll-free verification?