Skip to main content

Sends through the API and SMPP

Screen: API reports, address /analytics/api.

Everything your systems sent without a human opening the cabinet. Each list keeps to its own kind: sends made by hand are in the campaign list, sends made by your systems are here.

API report filters

Searching by your own identifier​

This is what makes the screen useful. A message sent through the API can carry your identifier — an order number, a ticket, whatever your system uses — and the search here finds by it.

That closes the loop: a customer complains about order 4815, you search for 4815, and you see whether the message went and what happened to it, without knowing anything about phone numbers or campaign numbers.

The channel filter​

The filter lists the channels your account sends through. Pick one to narrow the report down to it, and leave the filter alone to see them all together.

Why the period reaches into the future​

The default period on this screen extends beyond today, and that is deliberate. Deferred sends are usually scheduled through the API, so the report covers what has been accepted and is waiting to go as well as what has already gone.

If you see messages dated tomorrow, they are scheduled, not misdated.

SMPP​

Sends over an SMPP connection land in the same report, next to the ones made over HTTP. Which of the two carried a message matters while you are setting the integration up; to find a message, search by your identifier or by number.