Messaging service application programming interface
A system comprising: one or more processors and executable instructions accessible on a computer-readable medium that, when executed, cause the one or more processors to perform operations comprising: receiving from a client application executing on a client device a transmission request including an identifier associated with a recipient device; adding the transmission request to an outbound queue based on determining the transmission request is valid; causing transmission to the recipient device based on the transmission request being included in the outbound queue; obtaining status information specifying a status of transmission the status information including an indication of successful transmission; and storing a record of the transmission responsive to the causing the transmission the storing the record including storing a message and the indication of successful transmission.
1. A system comprising:
one or more processors and executable instructions accessible on a non-transitory machine readable medium that, when executed, cause the one or more processors to perform operations comprising:
receiving from a client application executing on a client device a transmission request including an identifier associated with a recipient device;
adding the transmission request to an outbound queue based on determining the transmission request is valid;
causing transmission to the recipient device based on the transmission request being included in the outbound queue;
obtaining status information specifying a status of transmission the status information including an indication of successful transmission; and
storing a record of the transmission responsive to the causing the transmission the storing the record including storing a message and the indication of successful transmission.
2. The system of claim 1 wherein the causing transmission comprises transmitting a request to a Short Message Service (SMS) aggregator the request identifying the identifier and a carrier associated with the recipient device the SMS aggregator to route the message to the carrier.
3. The system of claim 1 wherein a predefined messaging standard specifies a particular format for the message.
4. The system of claim 1 , wherein the message is transmitted as a Short Message Service (SMS) message.
5. The system of claim 1 wherein the message transmission request is a Hypertext transfer Protocol (HTTP) request.
6. A method comprising:
receiving from a client application executing on a client device a transmission request including an identifier associated with a recipient device;
adding the transmission request to an outbound queue based on determining the transmission request is valid;
causing transmission to the recipient device based on the transmission request being included in the outbound queue;
obtaining status information specifying a status of transmission the status information including an indication of successful transmission; and
storing a record of the transmission request responsive to the causing the transmission the record including storing a message and the indication of successful transmission of the message.
7. The method of claim 6 further comprising determining that the identifying is valid by determining that the identifier includes a particular number of characters.
8. The method of claim 6 , wherein the causing transmission comprises transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the identifier and a carrier associated with the recipient device, the SMS aggregator to route the message to the carrier.
9. The method of claim 6 , wherein a predefined messaging standard specifies a particular format for the message.
10. The method of claim 6 , wherein the message is transmitted as a Short Message Service (SMS) message.
11. The method of claim 6 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.
12. A non-transitory machine-readable medium comprising instructions which, when executed by a machine, cause the machine to perform operations comprising, at least:
receiving, from a client application executing on a client device, a transmission request including an identifier associated with a recipient device;
adding the transmission request to an outbound queue based on determining the transmission request is valid;
causing transmission to the recipient device based on the transmission request being included in the outbound queue;
obtaining status information specifying a status of transmission, the status information including an indication of successful transmission; and
storing a record of the transmission request responsive to the causing the transmission, the storing the record including storing a message or the indication of successful transmission of the message.
13. The medium of claim 12 , wherein the operations further comprise determining that the identifier is valid by determining that the identifier includes a particular number of characters.
14. The medium of claim 12 , wherein the causing transmission of the message comprises transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the identifier and a carrier associated with the recipient device, the SMS aggregator to route the message to the carrier.
15. The medium of claim 12 , wherein a predefined messaging standard specifies a particular format of the message.
16. The medium of claim 12 , wherein the message is transmitted as a Short Message Service (SMS) message.
17. The medium of claim 12 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.