Wire2Air developer docs
Send and receive SMS and MMS from your own software with the Wire2Air REST API, the legacy HTTP API and webhooks.
Wire2Air offers two APIs for sending and receiving text messages, plus webhooks that Wire2Air calls on your server when something happens.
| REST API v1 | HTTP API (legacy) | |
|---|---|---|
| Base URL | https://msgapi.wire2air.com/rest/v1 | Several hosts, one URL per endpoint |
| Credential | REST API key, in the apikey header | User ID, password and VASID, or an app key, as request parameters |
| Responses | JSON with HTTP status codes | Plain text, such as JOBID: … or ERR: 301: … |
| Covers | Sending SMS (single and bulk), listing received messages, managing campaigns | Sending SMS and MMS, credit balance, carrier lookup, keywords, subscribers, campaign invitations |
Start with the REST API v1 when it covers what you need. Use the HTTP API for the functions that only it documents, such as sending MMS, checking your credit balance or looking up a carrier.
Quick start
- Get your credentials from the Wire2Air dashboard.
- Send your first message with one
curlcommand. - Set up a webhook to receive replies and delivery reports.
curl "https://msgapi.wire2air.com/rest/v1/message" \
-H "apikey: YOUR_API_KEY" \
--data-urlencode "to=12121234567" \
--data-urlencode "from=27126" \
--data-urlencode "text=Hello from Wire2Air"
Find what you need
- Getting started: credentials and your first message, authentication, errors, rate limits.
- Guides: character encoding and message length, bulk messaging, scheduling.
- REST API v1: conventions, send a message, list received messages, campaigns.
- Webhooks: how callbacks work, inbound SMS, inbound SMS and MMS, delivery reports.
- HTTP API (legacy): overview, send SMS, send MMS and seven more endpoints.
- Integrations: RSA Authentication Manager, Zapier.
Before you go live
- Keep credentials on your server. Never put an API key, password or app key in a web page, a mobile app or a URL that ends up in logs.
- Use the
https://URLs on these pages. The few endpoints that are only documented over plainhttp://carry a warning. - Read Character encoding and message length: one non-GSM character switches a whole message to Unicode and cuts each part from 160 to 70 characters.
What changed in these docs
These pages replace the previous developer documentation at the same addresses; old links redirect here. The changelog lists what was corrected.