Our aim was to provide an API that implements all the features supported by our back end and ultimately exceeded those of our own website.
Now that it’s up and running, we’re so pleased with our API, we’re using it ourselves as a core part of the MOO technology stack.
- 12/Mar/2012 - Added documentation relaxing the required permissions slightly to allow API clients to read and update packs created with their own key. Once the end-user opens a drop-in URL in their browser, they take ownership of the pack, following which the API client cannot use it again (to avoid the ability for the API client to get extra personal details without the customer's knowledge)
- 12/Mar/2012 - Added documentation detailing the ability to modify the physical specification of a pack with the new moo.pack.updatePhysicalSpec call, using the new Physical Specification model.
- 12/Mar/2012 - Remove the need to perform 3-legged OAuth authentication. All existing integrations will continue to work, but now only need to perform 2-legged authentication. More details at Authentication
- 21/Mar/2011 - Add information about the new Order Tracking feature.
- 09/Mar/2011 - Update the documentation on moo.image.uploadImage to be clearer about the fact it's a multipart form POST
- 28/Feb/2011 - Publish the "Show API JSON" Greasemonkey script to aid API developers in working out a Pack data model appropriate for them.
- Support for all products
- You can use the API yourself, or provide a UI for your customers to use
- Use any of MOO's templates or create your own design and upload as a full side design
- Double sided printfinity for all products
- Flexible card distribution - you specify how many of each card should appear in a pack
- You can either provide MOO a fully designed pack, or you can partially design the pack and drop into MOO's UI so we finish the job*
- Either design your cards in an 'all in one' API call, or make several calls as part of a stateful step by step process*
- Checkout and shipping via the MOO cart
- You retain full rights and ownership of your images and designs
- The API method calls are provided by JSON-RPC style service
- Security is through OAuth
* some restrictions apply, eg. our UI does not support double sided printfinity. By default, new API accounts only have the ability to make 'all in one' calls - contact MOO if you would like your account upgraded to add extra permissions.