An API is a defined interface that allows two systems to exchange requests and responses. It makes a function in one product available from the workflow of another.
Requests, endpoints and responses
An endpoint describes where a particular action is available. A system sends data in an agreed format, and the API returns a status and relevant fields. The documentation explains what is required and how errors should be interpreted.
Authentication protects access
The Intellipush REST API uses OAuth 2.0. The client ID and secret should be held server-side, not in public browser or application code. Give systems and people only the access they require.
SMS as part of the workflow
An order, booking or other event can trigger a relevant message. Plan validation, duplicate control, error handling and limited logging before putting the integration into production.
A simple example
When a booking is confirmed, the booking system can send the required data to the SMS API. The API responds to the technical request, while the system retains responsibility for the event, wording and subsequent failure handling. This separation is easier to understand than business rules hidden across several services.
Questions before choosing an API
Look for current documentation, understandable authentication, clear error responses and a supplier able to clarify responsibilities and recipient-data processing. Intellipush includes API access with every account, uses OAuth 2.0 and publishes open developer documentation as the technical starting point.
A relevant next step
Planning an SMS integration?
See how the REST API, OAuth 2.0 and a clear operating model fit together.
