Connect your Telnyx account

Paste an API key to connect read-only, then grant write access when you want VICIfast to configure things for you. This is what we create on your account, what we never touch, and how to check it worked.

Connecting a carrier account means handing over an API key to something that spends real money, so the flow is deliberately built in two steps. You connect read-only first and nothing on your Telnyx account changes. Later, when you want VICIfast to configure things for you, you grant write access as a separate, explicit decision. About five minutes.

Get an API key from Telnyx

1
Sign in to portal.telnyx.com.
2
Open API Keys under your account settings.
3
Create a key and copy it. Telnyx shows it once, so paste it somewhere safe on the way.

Telnyx keys are account-wide — there is no read-only variant. That is why read-only is enforced on our side: in read-only mode the code that writes to your account is not reachable at all, rather than being asked politely not to run.

Connect it to VICIfast

1
In VICIfast, click Smart Carrier in the left sidebar, then Overview.
2
Click Connect account.
3
Paste the API key and give the account a label you will recognise later.
4
Click Connect. We verify the key against Telnyx immediately and show you the account name and balance, so you can confirm you connected the right one before going further.

At this point VICIfast can read your numbers and your balance and nothing else. Your numbers appear on the Phone Numbers page with whatever routing they already have, untouched.

Grant write access

Write access is what lets VICIfast configure your account — buy numbers, point them at your dialer or an AI agent, send texts, place calls. Turn it on from the account card on the Overview page.

The moment you grant it, we provision everything the product needs in one pass, rather than creating objects lazily the first time each feature is used. Every object we create is named with a VICIfast prefix, so you can tell ours from yours in your own portal at a glance:

VICIfast Outbound — an outbound voice profile. Everything we dial goes through this one, so our automated calls never inherit spend limits or destination rules you set for something else.
VICIfast Calls — a Call Control application. This is what AI calls, voicemail drops and Journey calls run under, and it carries the webhook we listen on.
VICIfast Messaging — a messaging profile that owns the inbound webhook, so replies to your texts arrive in the VICIfast inbox.
VICIfast <your hostname> — one SIP connection per dialer, with generated credentials, so your agents can dial out through this account.

Outbound dialing is set up for you

Granting write access also creates the outbound trunk on each of your dialers and the SIP connection it authenticates to. There is nothing to copy between two portals: the credentials are generated, the connection is created with the outbound voice profile already attached, and the trunk is installed on the box.

If you have more than one VICIfast server, you get one SIP connection and one trunk per server, each named after that server’s hostname. That is not a preference — Telnyx SIP credentials belong to a connection, so two dialers sharing one could not be told apart in your call records, could not be disabled independently, and rotating credentials for a rebuilt box would break every other box at the same moment. Connections cost nothing on Telnyx, so the only thing one-per-server costs you is a longer list, and that list reads by hostname.

A server you buy later is trunked automatically when it comes up, because connecting the carrier before buying the dialer is a perfectly ordinary order to do things in.

One step is still yours: pointing a campaign at the trunk. Open your server, go to Manage Trunks, and link the trunk to the campaigns that should dial through it. That step refuses to overwrite a dial prefix you already set, which is deliberate — we will not silently repoint a campaign that is already dialing somewhere.

What we never touch

Anything you built yourself. We match our own objects by the VICIfast name and by ids we recorded when we created them — never by "whatever exists". If you already have a SIP connection wired to your dialer, we leave it exactly as it is and say so on the Overview page rather than adopting it.

The same rule applies to numbers. A number already pointing somewhere you configured is reported as "routed outside VICIfast" and left alone until you explicitly attach it.

Check it worked

The Overview page runs a diagnosis across both sides at once — your carrier account and your dialer — which is the whole point of it living here. Nobody standing in the Telnyx console can see the dialer, and nobody in the dialer admin can see Telnyx.

Findings are deliberately conservative: one only appears when the mismatch can be proven. Silence means nothing provably wrong, not that nothing was checked.

If the balance runs out

Calls and texts stop at the carrier. VICIfast will keep reporting the failures — you will see them on the call in Analytics or as a failed step in a Journey — but topping up is something only you can do, in your own Telnyx portal.