The InkMonk service is for companies or organizations that want to distribute branded merchandise but don't have the time, funds, or human resources to create, package, and ship them all. Inkmonk solves this issue, allowing users to create, manage, and send swag to their audience. Using the InkMonk API, developers can integrate the InkMonk service, using simple calls. The different API parameters include a SKU call for individually identifying each design type, merchandise for identifying and managing products, a recipient call for tracking address and buyer information, and a shipment function for automating shipping orders. InkMonk requires an API key for use, and the API communicates over HTTP in JSON formats.
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