How to connect, route, bill and settle on PacketExchange, answered in plain terms. Cannot find it here? Open a ticket and we reply by email.
Accounts, credentials, trunks and the first call.
SIP trunks for voice, SMPP binds or the REST API for SMS. Credentials are issued the moment you buy a route and are live on our edge within a minute.
Minutes. Open an account, take your API key, top up, and send your first call or SMS. No sales call, no contract.
No. You need termination, and it can come from the marketplace or from a carrier you contract yourself.
No. Any valid E.164 caller ID is accepted by default, so you can build and test the call path before buying a single number.
Yes. The Verify API creates the code, sends it by text or by a call that reads the digits aloud, and checks what the user types. Only a hash of the code is stored.
POST /verify/start · POST /verify/checkThe send-time result first: accepted by the route, or failed with the reason. Where the route returns a carrier delivery receipt, the message then moves to delivered or failed (a failed message is refunded); on routes that return none it stays sent. GET /comms/sms/{id} shows the timeline.
The number catalogue does not flag SMS support per number yet. If you need a number for texting, ask support before you buy.
Which route carries a call, and whose carrier is behind it.
Check the status page first. Every service, from voice termination and SMS to the API and payments, is probed each minute and published with 90 days of history and any open incident.
Every route lists the ASR, ACD and PDD its seller states, next to our Exchange Score: a 1-100 rating we calculate from those stated figures and the route's tier once it has carried traffic, so you can weigh quality as well as price.
Either, and you can do both. Same carrier, two jobs.
Every call to you comes from PacketExchange, never from the buyer, so you allow our addresses once and every buyer can reach you. Allow all of them, for signalling and for media.
Allow our IPs on your switch
Every call reaches you from PacketExchange, never from the buyer. Allow all of these addresses, for signalling and for media.
144.76.120.84138.201.81.168Calls are shared across the addresses, so allowing only one makes about half of them fail.
Our price to you, and your price to your own users.
No. Both draw from the same wholesale market at the same rates. The platform fee depends on how traffic reaches us, not on who you are.
Yes. Create sub-accounts for your users and set your own retail price above the wholesale rate.
Two operational questions come with sub-accounts: how a call is attributed to a customer, and where its SIP password comes from. Both are in troubleshooting.
Balances, CDRs and margin, on both sides of the book.
Yes. Most operators do both: buying termination for their own app on one destination while selling their own routes on another.
Prepaid balances, platform fees and settlement on delivery are set out in developer pricing.