21216: API: Call blocked by Twilio

Twilio blocked the outbound call before connecting it to the destination. This error can occur when the destination is classified as high risk for fraud, when the route cannot be used for regulatory reasons, or when you place a call to a +1 destination without a valid Primary Customer Profile on your account.

• The destination is in a high-risk fraud range that Twilio blocks to reduce exposure to toll fraud.
• Regulatory restrictions prevent calls to the destination.
• Your account is placing a call to a +1 destination and does not have a valid Primary Customer Profile. This can occur when:
  • Your account does not have a Primary Customer Profile.
  • Your account has an Individual Customer Profile that was approved after October 2025. Individual profiles approved after this date do not satisfy the Primary Customer Profile requirement for +1 calling.

• If the destination is legitimate and appears to be blocked in error, contact Support from Console or through the Help Center and include the destination number and your business use case.
• If you need to place calls to +1 destinations, verify that your account has a Primary Customer Profile in Trust Hub on the main account in Console. If your account only has an Individual Customer Profile approved after October 2025, create a Business Customer Profile and submit it for review, then retry the call after the profile reaches Twilio Approved status. For more details, see Calls blocked by Twilio due to Primary Customer Profile requirements.
• Review your Voice Dialing Geographic Permissions and enable only the countries and number ranges you expect to call. This reduces your exposure to toll fraud.
• Validate destination numbers in your application and rate-limit outbound call requests so abusive traffic is less likely to trigger fraud controls.

• Dialing Permissions overview
• Console: Create a Primary Customer Profile
• Calls blocked by Twilio due to Primary Customer Profile requirements
• Anti-Fraud Developer's Guide