Integration guide

Set up Telnyx in RouteIQ

Connect a Telnyx number and dedicated messaging profile for outbound SMS and verified inbound replies.

Updated September 3, 2026
Use a dedicated messaging profile. RouteIQ assigns the profile's webhook to one RouteIQ site. Every number on that profile will send its inbound events to that site.

Before you start

You will need a verified and funded Telnyx account, a messaging-capable number, a messaging profile, any required carrier registration, and RouteIQ administrator access.

Review Telnyx's phone-number configuration guide.

1. Prepare a dedicated messaging profile

  1. Create a messaging profile for this RouteIQ site.
  2. Assign the sending number to that profile.
  3. Record the number in E.164 format and copy the profile's UUID.
  4. Complete required registration, such as US 10DLC or toll-free verification.
Incoming messages will be sent to RouteIQ

Saving or syncing updates the Telnyx setting for incoming messages so they reach your RouteIQ site. Do not share this profile with another site or app that needs to receive those messages.

2. Create the API key and copy the public key

  1. In Telnyx Mission Control, open API Keys.
  2. Create an API v2 key and copy it when shown.
  3. Open Keys & Credentials > Public Key.
  4. Copy the base64 Ed25519 webhook public key. Do not add PEM markers.

See Telnyx's guides to API v2 keys and signed webhooks.

3. Connect Telnyx to RouteIQ

  1. Sign in to RouteIQ and open Settings > Integrations.
  2. Find Telnyx and turn it on.
  3. After it shows Connected, select Configure.
  4. Enter the API Key, From Phone Number, Messaging Profile ID, and Webhook Public Key.
  5. Leave Is Active selected and save.

4. Verify the setup

  1. Select Sync. This checks the keys, phone number, messaging profile, and incoming-message setup.
  2. Send a test SMS from RouteIQ to a number you control.
  3. Reply and confirm the inbound message reaches RouteIQ.
  4. Check Telnyx Message Detail Records for acceptance and delivery.

Troubleshooting

The public key is rejected

Copy the complete base64 public key only. RouteIQ expects a value that decodes to a 32-byte Ed25519 key.

The number and profile do not match

Assign the exact number to the messaging profile entered in RouteIQ.

The profile is already in use

Create a separate Telnyx messaging profile for this RouteIQ site.

Outbound works but inbound does not

Select Sync, then confirm nobody changed the profile webhook afterward.

Rotate or remove credentials

  1. Create a replacement API key.
  2. Update RouteIQ, select Sync, and test both directions.
  3. Revoke the old API key after the tests pass.

If rotating the webhook signing key, update RouteIQ as soon as Telnyx activates the new public key. See Telnyx's signing-key rotation guide.