# TelecomsXchange Help Center > Official help center for the TelecomsXchange (TCXC) wholesale telecom marketplace: buying and selling voice routes, SMS (SMPP), IoT (MQTT), phone numbers (DIDs) and eSIMs, HLR lookups, and the REST API. Articles are Markdown; each page also exists at .md. Synced with platform build 83b4ebc9. ## For Buyers - [Getting started as a buyer on TelecomsXchange](https://help.telecomsxchange.com/buyers/getting-started.md): On the login page, use the Buyer Login panel: enter your Username and Password and click Sign In as Buyer. The Dashboard shows your balance, live calls and API keys, and the left sidebar takes you to every buyer tool. - [Create your first SIP, SMPP or IoT account](https://help.telecomsxchange.com/buyers/create-your-first-account.md): Go to Accounts → Add New Account, pick SIP, SMPP or IoT (MQTT), enter an Account Name, then authorize your system with an IP address, a generated login and password, or both. Choose whose balance it uses and click Add Account. An "Account added" card confirms it. - [Add funds: top up by card, PayPal or wire](https://help.telecomsxchange.com/buyers/add-funds.md): Click the + next to your balance, choose Credit / Debit Card, PayPal or Wire Transfer and click Confirm Payment Method. Pick the account and amount, then pay. Card and PayPal top-ups are credited after payment; wires and Interac e-Transfers usually within 1–3 business days. - [Find and buy routes in Market View](https://help.telecomsxchange.com/buyers/find-and-buy-routes.md): Open Market View, choose Voice Market or SMS Market, search by country, prefix, seller or description and compare the routes; prices already include the platform commission. Click Purchase, pick All Accounts or one account and click Confirm Purchase. You then pay per call or message from your balance. - [Send your first call with a tech prefix](https://help.telecomsxchange.com/buyers/send-your-first-call.md): Send calls from an authorized account to sip01.telecomsxchange.com port 5060 and dial the route's tech prefix before the E.164 number, for example 80039#447700900123. Each route's tech prefix is in My Interconnections and in the Purchased Route Confirmation email. - [Routing groups and route testing](https://help.telecomsxchange.com/buyers/routing-groups-and-route-testing.md): Go to Routing → Routing Groups, click Add New Routing Group, pick a policy, then add your purchased routes to the group. Dial the group's 444 tech prefix and the group picks the route for each call. - [Send SMS over SMPP and read your SDRs](https://help.telecomsxchange.com/buyers/send-sms.md): Bind as a transceiver to smpp01.telecomsxchange.com, TCP port 2776, with your account's SMPP System Id and SMPP Password. Put the route's tech prefix in front of the destination number (80039#447700900123), or send the plain number to use the account's default route. Each message segment is billed at the route's price; Logs → SDR (SMS) shows every message, its status, delivery time and cost. - [Connect IoT devices over MQTT and read your IDRs](https://help.telecomsxchange.com/buyers/iot-mqtt.md): Create an account with Protocol Type IoT (MQTT), then connect your devices to the broker with the generated MQTT Login and MQTT Password, using the host and port shown in the mosquitto_pub sample on the account's page. Every message published or delivered is charged a flat per-message fee to the account's balance. Logs → IDR (MQTT) lists each message with its topic, direction, status and cost. - [Buy and manage virtual phone numbers (DIDs)](https://help.telecomsxchange.com/buyers/virtual-numbers-dids.md): Go to DIDs → Market View, search by prefix, country or description, click Buy, enter the SIP endpoint for a voice number or the SMPP endpoint for an SMS number, choose the billing account and click Complete Purchase. The setup fee and first recurring fee are charged straight away. - [Buy and manage eSIMs](https://help.telecomsxchange.com/buyers/esims.md): Go to eSIMs → Market View, search by country, region or Global, click Purchase on a package, choose the account to pay from and click Confirm Purchase. The eSIM is issued at once with a QR code and LPA code to install it. My eSIMs shows the data and days left and lets you top up. - [Check a phone number with HLR Lookup](https://help.telecomsxchange.com/buyers/hlr-lookup.md): Go to Routing → HLR Lookup, enter the number in international format without + (for example 14155551234), choose the billing account and click Perform Lookup. Each lookup costs $0.05 from that account and shows the country, carrier, MCC/MNC, ported status and roaming status. - [Get started with the API](https://help.telecomsxchange.com/buyers/api.md): Tick Allow API Access in Profile & Preferences and copy your API key. Call https://apiv2.telecomsxchange.com with HTTP Digest authentication (your username, and the API key as the password). In four calls you can read your balances, search Market View, buy a route and pull your call records. The API reference documents every endpoint. - [Call records (CDRs), live calls and daily stats](https://help.telecomsxchange.com/buyers/call-records-and-live-calls.md): Go to Logs → CDR (Voice), set the prefix, call status and dates, and click Search CDRs; click Download to export them as CSV. Live Calls shows calls in progress, and Calls Stats (Voice) has daily files, plus weekly files every Monday. - [Preferences, email notifications and messaging sellers](https://help.telecomsxchange.com/buyers/preferences-notifications-messages.md): Go to Settings → Profile & Preferences, change your login, security, API and email settings, and click Update Preferences. Login Timeout is the idle auto-logout in minutes (0 = never). To contact a seller, open their profile, click Send Message, and read replies under the envelope icon. - [Invite your team and review who logged in](https://help.telecomsxchange.com/buyers/web-users-and-access-logs.md): Go to Settings → Web Users and click Invite New User. Enter the email, a phone number for two-step verification, a name and the role, and click Send Invitation. The person gets a "Welcome to TCXC" email with a link to choose their own username and password. Logs → Web Access shows every page request made on your account for the last 30 days. ## For Sellers - [Getting started as a seller on TelecomsXchange](https://help.telecomsxchange.com/sellers/getting-started.md): Open the Seller Account login, enter your Seller Login and Password and click Sign In. The Dashboard shows your balance, last payout, live calls and API keys; Settings → Profile & Preferences is where you finish your profile. - [Add your first route to sell](https://help.telecomsxchange.com/sellers/add-your-first-route.md): Go to Routes → My Routes, click Add New Route, choose VOICE (SIP) or SMS (SMPP), fill in the name, IP Address:Port, capacity and route type, and click Add Route. The route starts with an empty tariff, so upload your rates next. Edit Route holds number translation, OBR, caller ID policy and your subscribed buyers. - [Upload your rate deck (tariff CSV)](https://help.telecomsxchange.com/sellers/upload-your-rate-deck.md): In Routes → My Routes, open Edit Route, click Download current rates (CSV), edit it in a spreadsheet, choose it under Upload Tariff and click Update Settings. Voice rate increases take effect 6 days after upload; buyers get the changes by email. SMS routes can also take an MCCMNC price file. - [Whitelist TelecomsXchange on your switch (Interconnect Info)](https://help.telecomsxchange.com/sellers/interconnect-info.md): Go to Routes → Interconnect Info. Whitelist the TelecomsXchange platform IP, 174.136.44.213, on your firewall and switch. Voice arrives by SIP over UDP from source ports 5060–5072 with all codecs passed through; SMS arrives by an SMPP transceiver bind to your server. Each of your routes has a card with its exact destination, tech prefix and SMPP system ID. - [Manage your buyers and make private offers](https://help.telecomsxchange.com/sellers/manage-buyers-and-private-offers.md): Go to Routes → My Buyers to see who bought your routes or DIDs and message them. Replies arrive in your Messages inbox. To block a buyer or sell a route privately, open the route's Edit Route page and use Subscribed Buyers or Private Exchange. - [Quality thresholds, automatic blocks and anonymous routes](https://help.telecomsxchange.com/sellers/quality-thresholds-and-anonymous-routes.md): In Edit Route, fill in Minimum Traffic Requirements and click Update Settings. Each day TelecomsXchange checks every buyer's previous-day traffic on the route and blocks buyers below your ASR or ACD limits. Anonymous routes and DIDs cost a monthly fee taken from your balance. - [Sell SMS routes over SMPP](https://help.telecomsxchange.com/sellers/sell-sms-routes.md): Add a route with Protocol SMS (SMPP), enter your SMSC's IP and port and the system ID and password TelecomsXchange should bind with, and set the session timeout, enquire-link interval and the field your SMSC reads messages from. TelecomsXchange binds to you as a transceiver from 174.136.44.213. Upload a per-message rate deck, then watch Bind Status and the SDR (SMS) page. - [Sell virtual phone numbers (DIDs)](https://help.telecomsxchange.com/sellers/sell-virtual-numbers.md): Point your numbers to sip01.telecomsxchange.com (UDP 5060) or smpp01.telecomsxchange.com (TCP 2776). Then go to DIDs → My DIDs → Sell New DID, enter the number, prices and features, and click Publish DID. Update listed numbers in bulk with Upload CSV File. - [Sell eSIMs](https://help.telecomsxchange.com/sellers/sell-esims.md): eSIM providers sell their own inventory on TelecomsXchange. Once eSIM selling is enabled on your seller account, go to eSIMs → Config, choose the Provider Type your platform's API uses (eSimplified or Airalo), enter its API base URL, client ID and client secret, click Save Configuration, then Test Connection. Your packages are listed automatically at your price plus the platform commission, and eSIMs → Sales shows each order. - [Get paid: request a payout](https://help.telecomsxchange.com/sellers/get-paid.md): Go to Money → Withdraw Funds, choose how you want to be paid, enter the amount, click Send Payout Request and confirm. The fee is taken from your balance straight away and you're asked to email an invoice to billing@telecomsxchange.com; a transfer to your own buyer account arrives instantly. - [Check a phone number with HLR Lookup](https://help.telecomsxchange.com/sellers/hlr-lookup.md): Go to HLR Lookup in the sidebar, enter the number in international format without + (for example 14155551234) and click Perform Lookup. Each lookup costs $0.05 from your seller balance and shows the country, carrier, MCC/MNC, ported status and roaming status. - [Get started with the API](https://help.telecomsxchange.com/sellers/api.md): Tick Allow API Access in Profile & Preferences and copy your API key. Call https://apiv2.telecomsxchange.com with HTTP Digest authentication (your username, and the API key as the password). Read your balance and payout history, manage the numbers you sell and message your buyers. The API reference documents every endpoint. - [Seller reports, live calls and preferences](https://help.telecomsxchange.com/sellers/reports-and-preferences.md): Use Logs → CDR (Voice) to see and download every call on your routes, Live Calls to watch calls in progress, and Logs → Call Stats (Voice) for daily files. Settings → Profile & Preferences holds your logo, report emails, login timeout, API access and payout method. - [Invite your team and review who logged in](https://help.telecomsxchange.com/sellers/web-users-and-access-logs.md): Go to Settings → Web Users and click Invite User. Enter the email, a phone number for two-step verification, a name and the role, and click Send Invitation. The person gets a "Welcome to TCXC" email with a link to choose their own username and password. Finance users can withdraw funds; other roles can't. Logs → Web Access shows every page request on your account for the last 30 days. ## Integrations - [Connect a SIP platform to TelecomsXchange](https://help.telecomsxchange.com/integrations/connect-sip-platforms.md): TelecomsXchange is SIP peering only: it never accepts REGISTER. To buy, send INVITEs over UDP to sip01.telecomsxchange.com port 5060 from an authorised IP, or answer the digest challenge with the account's VoIP login, and dial the tech prefix before the E.164 number (80039#447700900123). To sell or receive numbers, accept SIP over UDP from 174.136.44.213, source ports 5060 to 5072. - [Connect Asterisk to TelecomsXchange](https://help.telecomsxchange.com/integrations/asterisk.md): Create a PJSIP endpoint, aor and identify for sip01.telecomsxchange.com on UDP 5060 with no registration, matching 174.136.44.213 for inbound. Authorise your public IP on the TelecomsXchange account or add an outbound_auth with the VoIP login, and dial PJSIP/TECH_PREFIX + E.164 number. - [Connect FreeSWITCH to TelecomsXchange](https://help.telecomsxchange.com/integrations/freeswitch.md): Add a Sofia gateway on the external profile with proxy sip01.telecomsxchange.com:5060 and register=false, then bridge to sofia/gateway/tcxc/TECH_PREFIX followed by the E.164 number. Authorise FreeSWITCH's public IP on the account, or put the VoIP login and password on the gateway; accept inbound calls only from 174.136.44.213. - [Connect Kamailio to TelecomsXchange](https://help.telecomsxchange.com/integrations/kamailio.md): Put sip:sip01.telecomsxchange.com:5060 in a dispatcher set, rewrite the Request-URI user to TECH_PREFIX plus the E.164 number, and relay. Authorise Kamailio's public IP on the account, or answer 401/407 in a failure route with uac_auth() and the VoIP login. Accept inbound calls with allow_source_address() for 174.136.44.213. - [Connect OpenSIPS to TelecomsXchange](https://help.telecomsxchange.com/integrations/opensips.md): Add sip01.telecomsxchange.com:5060 as a drouting gateway whose pri_prefix is the route's tech prefix, normalise the number to E.164 and call do_routing(). Authorise OpenSIPS's public IP on the account, or answer 401/407 in a failure route with uac_auth() and the VoIP login. Accept inbound calls with check_source_address() for 174.136.44.213. - [Connect Sippy Softswitch to TelecomsXchange](https://help.telecomsxchange.com/integrations/sippy.md): In Sippy, add a vendor TelecomsXchange with a connection to sip01.telecomsxchange.com port 5060 and the CLD translation rule s/^/80039#/, then add it to a routing group. Authorise Sippy's public IP on the TelecomsXchange account or fill the connection's username and password with the VoIP login. To sell, create an account with an authentication rule for remote IP 174.136.44.213. - [Connect PortaSwitch to TelecomsXchange](https://help.telecomsxchange.com/integrations/portaswitch.md): In PortaBilling, add a vendor TelecomsXchange and a SIP connection, direction To vendor, remote IP 174.136.44.213 (sip01) port 5060 UDP, with tech prefix 80039# or the CLD translation s/^/80039#/. Authorise PortaSIP's public IP on the TelecomsXchange account, or attach a vendor authorization with the VoIP login. To sell, create a customer account whose ID is 174.136.44.213 for IP authentication. - [Connect Twilio to TelecomsXchange](https://help.telecomsxchange.com/integrations/twilio.md): Twilio isn't a switch you point at TelecomsXchange as a trunk. To buy, return TwiML to sip:TECH_PREFIX%23NUMBER@sip01.telecomsxchange.com with the account's VoIP login and password as username and password. To receive TelecomsXchange phone numbers, create a Twilio SIP domain with an IP access control list for 174.136.44.213 and set it as the number's SIP endpoint. - [Connect Telnyx to TelecomsXchange](https://help.telecomsxchange.com/integrations/telnyx.md): Telnyx isn't a switch you point at TelecomsXchange as a trunk. To buy, dial sip:TECH_PREFIX%23NUMBER@sip01.telecomsxchange.com from TeXML or the Call Control dial command, with the account's VoIP login and password as the SIP credentials. To receive TelecomsXchange phone numbers, give a Telnyx IP or FQDN connection a SIP subdomain that accepts calls from anyone, and set it as the number's SIP endpoint. - [Connect an SMPP platform to TelecomsXchange](https://help.telecomsxchange.com/integrations/connect-smpp-platforms.md): To send SMS, bind as a transceiver to smpp01.telecomsxchange.com, TCP 2776, SMPP 3.4, with your account's SMPP System Id and SMPP Password, and put the route's tech prefix before the number (80039#447700900123). To sell SMS, let TelecomsXchange bind to your SMSC as a transceiver from 174.136.44.213 with the system ID and password you set on your route. - [Connect Kannel to TelecomsXchange](https://help.telecomsxchange.com/integrations/kannel.md): Add a group = smsc with smsc = smpp, host = smpp01.telecomsxchange.com, port = 2776, transceiver-mode = true and your account's SMPP System Id and SMPP Password as smsc-username and smsc-password. Set unified-prefix = "TECH_PREFIX#,+,00" on that group so +447700900123 leaves as 80039#447700900123. To sell SMS, Kannel needs the opensmppbox add-on to accept TelecomsXchange's bind. - [Connect Jasmin SMS Gateway to TelecomsXchange](https://help.telecomsxchange.com/integrations/jasmin.md): In jCli, add an smppccm connector with host smpp01.telecomsxchange.com, port 2776, bind transceiver and your account's SMPP System Id and SMPP Password, then route to it with an MT route. Jasmin's HTTP API accepts only digits in to, so add the tech prefix with an MT interceptor script that rewrites destination_addr to 80039#447700900123. To sell SMS, create a Jasmin user with TelecomsXchange's credentials and let it bind to the SMPP Server API. - [Connect Restcomm SMSC to TelecomsXchange](https://help.telecomsxchange.com/integrations/restcomm-smsc.md): In the SMSC CLI, create a CLIENT ESME of bind type TRANSCEIVER to smpp01.telecomsxchange.com port 2776 with your account's SMPP System Id and SMPP Password, in its own networkId. An mproc rule moves your applications' messages into that networkId and adds the tech prefix with adddestdigprefix 80039#. To sell SMS, create a SERVER ESME for host 174.136.44.213 with the credentials you set on your TelecomsXchange route. - [Connect 3CX to TelecomsXchange](https://help.telecomsxchange.com/integrations/3cx.md): In 3CX V20, add a Generic SIP Trunk pointing at sip01.telecomsxchange.com port 5060 with authentication set to Do not require (IP based), and authorise 3CX's public IP on your TelecomsXchange account. Add an outbound rule that strips + or 00 and prepends the route's tech prefix, so calls leave as 80039#447700900123. - [Connect FreePBX to TelecomsXchange](https://help.telecomsxchange.com/integrations/freepbx.md): In FreePBX 17, add a chan_pjsip trunk to sip01.telecomsxchange.com port 5060 with Registration set to None and Authentication set to None (IP) or Outbound (VoIP login and password), and Match (Permit) 174.136.44.213. Add an outbound route that prepends the tech prefix, so calls leave as 80039#447700900123, and inbound routes for your E.164 numbers. - [Connect Yeastar P-Series to TelecomsXchange](https://help.telecomsxchange.com/integrations/yeastar.md): On a Yeastar P-Series PBX, add a SIP trunk of type Peer Trunk (not a register trunk) to sip01.telecomsxchange.com port 5060 over UDP, and authorise the PBX's public IP on your TelecomsXchange account. Add an outbound route that strips 00 and prepends the tech prefix, so calls leave as 80039#447700900123, and inbound routes for your E.164 numbers. - [Connect Grandstream UCM to TelecomsXchange](https://help.telecomsxchange.com/integrations/grandstream-ucm.md): On a Grandstream UCM6300 or UCM63xx, add a VoIP trunk of type Peer SIP Trunk to sip01.telecomsxchange.com over UDP with heartbeat detection off, and authorise the UCM's public IP on your TelecomsXchange account. Add an outbound rule that strips 00 and prepends the tech prefix, so calls leave as 80039#447700900123, and inbound rules for your E.164 numbers. - [Connect Cisco CUBE to TelecomsXchange](https://help.telecomsxchange.com/integrations/cisco-cube.md): On CUBE, add an outbound dial-peer to dns:sip01.telecomsxchange.com:5060 over UDP with a translation profile that replaces + or 00 with the tech prefix, and authorise CUBE's public IP or add authentication username VOIP_LOGIN on the dial-peer. Trust 174.136.44.213, match it with voice class uri and incoming uri via, and route those calls to CUCM. - [Connect VICIdial to TelecomsXchange](https://help.telecomsxchange.com/integrations/vicidial.md): In Admin → Carriers, add a carrier with a blank Registration String, an account entry for sip01.telecomsxchange.com on UDP 5060, and a dialplan entry that strips the campaign Dial Prefix and dials TECH_PREFIX + E.164 number. Authorise the dialer's public IP on the TelecomsXchange account (10 calls per second per IP), and route numbers you bought with Admin → Inbound DIDs. - [Connect Genesys Cloud to TelecomsXchange](https://help.telecomsxchange.com/integrations/genesys-cloud.md): Create a Generic BYOC Carrier external trunk with Protocol UDP, SIP server sip01.telecomsxchange.com port 5060, Digest Authentication with the account's VoIP login and password, and a called-address transformation that turns +447700900123 into TECH_PREFIX + 447700900123. Add it to a site's outbound route; for inbound, allow 174.136.44.213 and point numbers you bought at the trunk's inbound FQDN. - [Use TelecomsXchange with Amazon Connect](https://help.telecomsxchange.com/integrations/amazon-connect.md): Amazon Connect can't use an outside carrier as its trunk: its inbound and outbound PSTN calls go through numbers claimed or ported into Connect, and the Chime SDK Voice Connector is AWS's own SIP trunk, not a bridge to another carrier. To use TelecomsXchange numbers, deliver them to a SIP server you run (Asterisk, FreeSWITCH or an SBC) and forward each call to a number claimed in Connect, through a TelecomsXchange route over UDP. - [Connect Microsoft Teams Direct Routing to TelecomsXchange](https://help.telecomsxchange.com/integrations/microsoft-teams.md): Teams Direct Routing talks only TLS and SRTP to a Microsoft-certified SBC, so TelecomsXchange can't connect to Teams directly. Run an SBC such as AudioCodes Mediant or Ribbon: pair it with Teams using New-CsOnlinePSTNGateway, a PSTN usage, voice route and voice routing policy, and point its carrier side at sip01.telecomsxchange.com over UDP 5060, adding TECH_PREFIX and authenticating by IP or digest. - [Connect Zoom Phone BYOC to TelecomsXchange](https://help.telecomsxchange.com/integrations/zoom-phone.md): Zoom Phone Premise Peering (BYOC-P) peers Zoom's data centres with an SBC you run, over TLS on port 5061 with SRTP, so TelecomsXchange can't connect to Zoom directly. Add the SBC, a route group and a SIP group in the Zoom web portal and assign BYOC numbers; on the SBC's carrier side, send SIP over UDP to sip01.telecomsxchange.com port 5060 with TECH_PREFIX in front of the E.164 number, authorised by IP or digest. - [Connect VOS3000 to TelecomsXchange](https://help.telecomsxchange.com/integrations/vos3000.md): In VOS3000, add a static SIP routing gateway for sip01.telecomsxchange.com port 5060 and a routing callee rewrite rule with original prefix * and target prefix 80039#*, so 447700900123 leaves as 80039#447700900123. Authorise VOS3000's public IP on the TelecomsXchange account. To sell, add a static mapping gateway for IP 174.136.44.213 tied to a billing account with your rate group. - [Connect VoipSwitch to TelecomsXchange](https://help.telecomsxchange.com/integrations/voipswitch.md): In VoipSwitch (VSM), add a gateway for sip01.telecomsxchange.com port 5060 over UDP with Ping off, put the tech prefix (80039#) in its Dialed number prefix field, and point a routing plan entry at it. Authorise VoipSwitch's public IP on the TelecomsXchange account, or fill the gateway's User name and User password with the VoIP login. To sell, add a wholesale client with IP 174.136.44.213. - [Connect MOR (Kolmisoft) to TelecomsXchange](https://help.telecomsxchange.com/integrations/mor-kolmisoft.md): In MOR, add a SIP provider with Hostname sip01.telecomsxchange.com, Server IP 174.136.44.213, Port 5060, Authenticate by IP on and Register off, then add a provider rule that adds the tech prefix (80039#) and put the provider in an LCR. To sell, accept 174.136.44.213 as an IP-authenticated device for a user with your tariff, or assign the TelecomsXchange provider to that user if you also buy. - [Connect an AudioCodes Mediant SBC to TelecomsXchange](https://help.telecomsxchange.com/integrations/audiocodes-sbc.md): On the Mediant SBC, add a Proxy Set with sip01.telecomsxchange.com:5060 over UDP and Proxy Keep-Alive disabled, a Server-type IP Group for TelecomsXchange, an IP-to-IP routing rule to it, and an outbound manipulation that adds the tech prefix (80039#) to the destination URI. Authorise the SBC's public IP on the account, or add an Account with the VoIP login and Register set to No. Classify calls from 174.136.44.213 to the same IP Group. - [Connect a Ribbon SBC to TelecomsXchange](https://help.telecomsxchange.com/integrations/ribbon-sbc.md): On a Ribbon SBC Edge (SBC 1000/2000) or SBC SWe Lite, add a SIP Server Table entry for sip01.telecomsxchange.com port 5060 over UDP with Monitor set to None, a SIP signaling group that uses it with 174.136.44.213 as its Federated IP, a transformation table that turns (.*) into 80039#\1, and a call route to that signaling group. Authorise the SBC's public IP on the account, or add a Remote Authorization Table with the VoIP login. ## API reference - [Overview: base URL, authentication, errors, limits](https://help.telecomsxchange.com/reference/overview.md) - [OpenAPI 3.0 spec, verified](https://help.telecomsxchange.com/reference/openapi.json) - [Accounts](https://help.telecomsxchange.com/reference/accounts.md): Create a buyer account, Update a buyer account, Add an extra IP to an account - [Voice and SMS market](https://help.telecomsxchange.com/reference/market.md): Search Market View, Download a route's rate deck, Top destinations by traffic, List buyer accounts, Get test numbers, Start a route test call, List active calls, List call records (CDRs), List SMS records, Top destinations by traffic (buyers), Start a route test call (signed URL) - [Interconnects](https://help.telecomsxchange.com/reference/interconnects.md): Buy a route (create an interconnect), List interconnects - [Routing groups](https://help.telecomsxchange.com/reference/routing-groups.md): List routing groups, Create a routing group, Update a routing group, Add a routing rule, Update a routing rule, Delete a routing rule, Move a routing rule up, Move a routing rule down, Add a route to a group, Remove a route from a group, Move a route up, Move a route down, Set a route's weight - [Phone numbers (DIDs)](https://help.telecomsxchange.com/reference/numbers.md): Add a DID for sale, List your DIDs (seller), Update a DID you sell, Search the DID market, Purchase a DID, List purchased DIDs, Update a purchased DID's destination, Cancel a purchased DID - [eSIMs](https://help.telecomsxchange.com/reference/esims.md): List eSIM countries, Market View (eSIM), Purchase an eSIM, List top-up packages, Purchase a top-up, eSIM order history, List purchased eSIMs, List eSIM regions, List regions covering a country - [HLR lookups](https://help.telecomsxchange.com/reference/hlr.md): Look up a number (buyer), Look up a number (seller) - [Balances and payments](https://help.telecomsxchange.com/reference/money.md): List account balances, List payment history, Get seller balance, List payout history - [Reports](https://help.telecomsxchange.com/reference/reports.md): List IoT (MQTT) message records, Voice summary report, SMS summary report - [Messages](https://help.telecomsxchange.com/reference/messages.md): List buyer messages, Reply to a seller message, Send a message to a seller, List seller messages, List my buyers, Message my buyers, Send a message to a buyer, Reply to a buyer message - [Tools](https://help.telecomsxchange.com/reference/tools.md): List seller routes - [Message classification (AI)](https://help.telecomsxchange.com/reference/ai.md): Check message safety, Threat classifier health, Classify message category, Classify message categories in bulk, List categories, Category classifier health ## Optional - [All articles, one file](https://help.telecomsxchange.com/llms-full.txt) - [JSON API](https://help.telecomsxchange.com/api/articles.json) - [Every API endpoint, as JSON](https://help.telecomsxchange.com/reference/endpoints.json)