How to Use Twilio Verify Over Interconnect

December 17, 2025
Reviewed by

Organizations that need Twilio Verify traffic to travel over a private, dedicated network can use Twilio Interconnect to route traffic between their infrastructure and Twilio. This setup reduces exposure to the public internet and delivers enterprise-grade performance, reliability, and security, making it a good fit for teams with regulatory, fraud-prevention, or high-availability requirements.

This blog post provides a step-by-step guide for integrating Twilio Verify with Interconnect, from planning and requesting connectivity to configuring Verify services and validating end-to-end delivery.

Benefits of using Twilio Verify over Interconnect

There are many benefits of using Interconnect, but the most common reasons companies choose to send Verifications over Interconnect include:

  • Private connections to Twilio avoid transit across the public internet and can provide predictable Quality of Service (QoS).
  • Integrating Twilio Verify over Interconnect keeps your API traffic on a private path which provides a stronger network-level security.

Prerequisites and guidelines

  • An active Twilio account – with console access.
  • At least one Twilio Verify service enabled – create or configure a Verification Service in the Twilio Console. These instructions assume that you already have a working Verify account and are able to send OTPs successfully through the platform. For complete instructions please follow the Verify API reference doc.
  • Network readiness – infrastructure capable of supporting a VPN interconnect type.
This blog post applies to VPN type connections. You can also use Cross Connect to connect via fiber optics to Twilio partner infrastructure providers.
Instructions on ensuring backup connections with a button to add a new connection on the right.
  1. Log into Twilio Console: Go to the Interconnect provisioning page and click on the Add new connection button in the top-right corner.
  2. Select the VPN connection type for a simpler IPSec tunnel deployment.
  3. Name the connection.
  4. Submit Connection Details:
    1. VPN connection type
    2. Twilio Interconnect location, which is the entry point to the Twilio Super Network
    3. IP information
    4. Tunnel parameters
  5. You’ll get confirmation of submission and your requested connection will appear with status Established in the Connection requests section of the Interconnect Connections page.

Step 2: Work with the Interconnect team to setup your connection

The Twilio Interconnect team may request more information or corrections during the setup process. When your connection is ready you will be notified via a support ticket and your connection will appear in the Established connections section as Active.

Step 3: Configure and Use Twilio Verify

To update your API calls to use your interconnect edge, the only change you need to make is to add the private Interconnect edge in the API URL subdomain or when you initialize the SDK client:

Change

curl -X POST "https://verify.twilio.com/v2/Services/VAaaaaaaaaa/Verifications"

to

curl -X POST "https://verify.ashburn-ix.twilio.com/v2/Services/VAaaaaaaaaa/Verifications"

Use the new subdomain for each Verify API request you make, including VerificationChecks.

Example: Use Verify Over Interconnect in Node.js

const twilio = require("twilio");
const client = twilio(accountSid, authToken, {
    edge: "ashburn-ix" // Use the Interconnect edge
});
client.verify.services(serviceSid)
    .verifications
    .create({ to: "+15017122661", channel: "sms" })
    .then(verification => console.log(verification.sid));

Example: Using Verify Over Interconnect with cURL

curl -X POST "https://verify.ashburn-ix.twilio.com/v2/Services/VAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/Verifications" \
--data-urlencode "To=+15017122661" \
--data-urlencode "Channel=sms" \
-u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN

References

For more information on using and configuring Interconnect, check out the following documentation and references: