An SMS gateway connects an application with the infrastructure that delivers SMS. To a developer it commonly appears as an API, while the provider handles onward routing to the relevant mobile networks.
From system to recipient
The application authenticates, sends the recipient, sender and message to an endpoint, and receives a technical response. The gateway validates the request and attempts to route the message onward.
Status has several stages
An accepted API call does not necessarily mean that the message has been finally delivered. The integration should distinguish an accepted request, onward processing and available delivery status.
Choose for workflow and responsibility
Consider documentation, authentication, markets, support and error handling. Protect secrets, limit logging and resolve the processing of recipient data before production use.
Understand delivery status
Status values describe technical events and must be interpreted according to the documentation. Distinguish between a request being received, the message being processed and an available final status being recorded. Do not build customer promises on a status the integration has not checked or understood.
Intellipush as a gateway
Intellipush provides a portal and REST API using OAuth 2.0, supported by open developer documentation. API access is included with every account. Treat the documentation as the technical contract and contact the team when sender setup, markets, volume or the intended workflow requires clarification before production use.
A relevant next step
Planning an SMS integration?
See how the REST API, OAuth 2.0 and a clear operating model fit together.
