The service provides messaging, both one-to-one and one-to-many, via social media platforms -- Facebook, Twitter, and LinkedIn -- in addition to more traditional SMS text messaging and email. It allows the sender to assign individual recipients to groups called "yards" for shared management of communications. For example, an instructor can create one or more yards composed of students in a course to allow messaging between individuals, project groups within the course, or all students. Notification options allow delivery of time-sensitive information via the methods most convenient to both sender and recipient.
API methods support managing user accounts and group memberships, with notification options selected for each. Methods support creation, updating, distribution, and deletion of message content. Reporting functions provide full analytics about service usage and communication success.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at email@example.com
So far, we don't have a record of any changes to this API