Integration & API

Connect your system to ours

TelQ integrates directly into your SMS platform through either REST API or SMPP. Choose your integration method and run tests more easily.

Why integrate?

Reactive or proactive approach? You decide

Running tests manually through a UI means you only test when there is an issue or an escalation. Integrating TelQ with your platform, through an SMPP session or the REST API, allows you to set up scheduled tests and monitor routes proactively, before live traffic is affected.

Continuous monitoring

Trigger tests automatically on a schedule or from your own systems. Route quality is monitored around the clock, not just when an issue surfaces.

Works in your system

Trigger tests from your own platform via the REST API, or send them from TelQ's UI through your SMPP session. Either way your existing routing stays untouched.

Structured result data

Every test result, with delivery status, Sender ID, SMSC, delay and content, is available as structured JSON through the API and in TelQ's reports and exports. Feed it into your own analytics or alerting.

Real-time callbacks

Configure a callback URL in your API request or account settings and TelQ POSTs each result the moment its status changes. No polling required, your system reacts immediately.

You control the traffic

TelQ never connects to your suppliers directly. Tests always leave through your own channels, whether triggered via API or sent through your SMPP session. TelQ only reports what arrived on the handset.

Up and running fast

Official SDKs for Java, Python and PHP, plus cURL examples in the docs. REST API integration takes a few simple steps; SMPP is the fastest path if you already have an SMPP server.

Choose REST API for programmatic control, SMPP for direct platform integration, or connect through Alaris and Horisen. All methods deliver the same test result data.

SMPP integration

Connect directly to your SMPP server

SMPP integration lets you connect TelQ directly to your SMPP server, so you can send and schedule test messages straight from TelQ's UI without touching your existing setup.

If you already have an SMPP server, this is typically the fastest integration to get running. Two approaches depending on your infrastructure:

Approach 1 (recommended)

Route by service type or TLV params

One SMPP session (bind), several suppliers. Assign a unique Service Type or TLV params to each supplier in TelQ's UI. Your server routes on that parameter.

One SMPP session handles all suppliers
Full traffic control, TelQ never touches your suppliers
Bulk upload of sessions and suppliers via Excel
Fewer sessions to configure on your server
Approach 2

Route by session login

One SMPP session per supplier. Your server routes on the login of each session. More sessions to set up, but it works with any SMPP server.

Works with even the most basic SMPP servers
Full traffic control on your side
Bulk upload of sessions and suppliers via Excel
SMPP session
# TelQ binds to YOUR SMPP server

Host:     smpp.your-platform.com
Port:     2775
Login:    your_system_id
Password: •••••••• # stored encrypted on TelQ's side

# Optional: Service Type for routing per supplier
service_type = "SUPPLIER_A"

# Optional: TLV params (hex, no 0x prefix; TelQ adds the length)
tlv_tag   = 1400
tlv_value = 0001
SMPP integration guide

Connect once, test continuously

Start with a free trial and explore the API documentation, or talk to us about your specific setup.