From their site: Welcome to MOO. We're a printing company. Customers create a pack and then the pack is printed to pre-defined products. Create an XML document to determine where the user is placed in the process. For example, if you define a list of images that you want the user to select from to make a pack of cards, then they will be forwarded to the 'chooser' page. If you specify a list of images that you want them to actually use, and the 'crop' data associated with them then the user will be sent to the part of the process where they design the back of the cards.
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
15-12-15 11:20:16[SDK] MOO Ruby SDK by Ali updated with Related API MOO
15-12-15 11:19:16[SDK] MOO PHP SDK by Jonathan Oddy updated with Related API MOO