Knowledge Base

Sub-categories

1. DR_Forwarder
   The automatic forwarding of MT SMS delivery states to client servers.
2. LowBal_Notification
   The automatic notification when an account's balance drops down to/below a pre-specific level.
3. MO_Forwarder
   The automatic forwarding of MO SMS to client servers.
4. MO_Responder
   The routine through which dynamic responses to Mobile Originated SMS are made.
5. Subscription_State
   Routines through which our server communicates with client servers.

Tutorials

• How to receive an API-Client routine.
• How to respond to an API-Client routine in a timely manner.

Frequently Asked Questions

• What happens if our (client) server fails or takes too long to respond?
• How can I simulate an API-Client routine?

How to respond to an API-Client routine in a timely manner.

If the data from our requests are being processed/handled in an advanced manner, such as querying or fed into a database, the following sequence of events to be adopted:

1. Receive the request
2. Write the query string to a buffer.
3. Respond with the "200 OK" status to complete the HTTP transaction.
4. Handle the buffer data, ideally by an independent process.