At Harvard, we’re big fans of TextMarks. Not only have students been using SBOY for years to get shuttle schedules on demand, the underlying TextMarks API is so simple that we’ve introduced it in CS50 to teach students how to use APIs. ”
TextMarks SMS APIs allow you to send and receive text messages from your web or enterprise application using our shared shortcode.
Unlike SMS e-mail gateways which add ugly headers, limit your delivery rate, and can take hours to deliver your messages, our API gives you a reliable direct conduit to your users' mobile phones.
With our group management functionality, group text broadcast, and the ability to easily handle and respond to incoming SMS messages with scripts on your own server, you have the perfect text messaging solution for your app.
Use as little or as much of our API services as you need. Read more and see how TextMarks SMS API is just what you're looking for.
We offer three main services for developers looking to easily integrate SMS/text messages into their applications and web sites. They are listed here from simplest to most advanced, with more information on each below.
Anybody with basic web programming experience should be able to execute this type of integration.
Once a user engages with your keyword, they don't necessarily have to keep sending the keyword with each request. You can provide multiple choice questions or other interactions by telling the user e.g. "Rply A for cookies. Rply B for pizza." and the user need only reply with "A" or "B". Text STATEINFO to 41411 for an example of how simple and powerful this contextual response feature is.
For this type of integration, you should be somewhat familar with calling public web services. We offer API clients for common languages (PHP, Python, Java).
TextMarks powerful API provides programmatic access to practically everything you can do on our website. Clients have built entire complex text-messaging applications on top of our API. Even this web site itself uses our API!
Only experienced systems programmers should undertake complex TextMarks integrations. We recommend starting with Asynchronous Automated Messaging (see above), which is a subset of the full API package, and then building from there.