The Logicbroker Commerce API allows for seamless integration without you having to worry about custom formats or different connection points. it allows you to communicate through the entire order lifecycle with any partner using one connection endpoint, regardless of if the brand or retailer sends orders in EDI, XML, CSV, or JSON the same format will be consumed. If you are a brand or retailer sending orders through Logicbroker, the same works for the supplier; they can receive those orders in any format.
An API key is required for authentication and can be generated by logging in to the Logicbroker portal and going to Settings > API Authentication. Your Primary key is generally for your internal use whereas a secondary key can be shared with your 3rd party development or external resources.
A Webhook version of this API is also available.
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 firstname.lastname@example.org
07-11-18 17:13:43Description fixes
07-11-18 17:11:29Updated artwork, authentication, request and response formats, description.
30-03-17 14:33:00[Brief] Daily API RoundUp: Authentimate, OneLogin, Odd Networks, LBRY updated with Related API Logicbroker Commerce
30-03-17 11:14:52Updated API Endpoint to https://commerceapi.io/api/v1/, looks like it was incorrect.