An SMS API lets an application send messages and receive replies and delivery receipts over HTTP. smsswit.ch offers HTTP, XML and REST interfaces with webhooks, next to SMPP, so each client can pick the integration that suits it.
What the API covers
- Submitting messages over HTTP, XML or REST.
- Receiving MO traffic and delivery receipts by webhook.
- API keys locked to client IPs.
- Roles for admin, user and finance, and a log of every change.
- Billing and CDRs written on submit.
REST and webhooks
REST and webhooks are included in every plan. MO forwarding works over SMPP, HTTP or webhook, so traffic reaches the client, IVR or application that owns a number range.
When to use SMPP instead
For high-volume carrier and aggregator links, SMPP connectivity is usually the better fit. For developers building applications, the API is simpler. Both run on the same SMS gateway.
Frequently asked questions
Does the API return delivery reports?
Yes. Delivery receipts are mapped back to the origin of each message and can be delivered by webhook.
Can API keys be restricted?
Yes. API keys can be locked to client IP addresses.
See it with your own ranges
We build a demo account around your range structure, with test ranges and a simulated carrier, so you can send traffic and check billing before you commit. Ask about SMPP connections, partnerships or migration in the same request.