Сколько стоит dev.logicbroker.com?

Logicbroker Commerce API

The Logicbroker Commerce API provides your system insight into the entire order lifecycle using a single connection. Regardless of the file format your trading partner utilizes( EDI, CSV, XML, JSON) the API consumes and returns information in a single format (JSON/XML). This works for suppliers or retailers. The Commerce API eliminates the need to worry about partner-specific data formats, or endpoints. With Logicbroker: 1 Connection; 1 Format; Countless Partners # API Authentication To retrieve your API key, login to the logicbroker portal. An API Key can be generated by going to Settings > API Authentication Primary key is generally for your internal use where as the secondary key can be shared with your 3rd party development or external resources. An API Key will need to be generated in the **Production portal:**https://portal.logicbroker.comas well as the **Stage portal:**https://stageportal.logicbroker.com Every request must have the API key as a URL query parameter (subscription-key). # Understanding the Flow Logicbroker uses statuses to dictate document flow. Examples of order statuses are: New, Ready to be Acknowledged, Updating Address Information, Ready to Ship, Ready to Invoice, Complete etc. These statuses dictate when API calls need to be made to complete the order life cycle. The documentation is grouped as follows: 1. Retailers - Retailer Order LifeCycle - Retailer Inventory Process 2. Suppliers - Supplier Order Life Cycle - Supplier Label Flows - Supplier Inventory Process 3. Other System Data - Product Content - Activity Events and Error Handling - Webhooks These sections will help you understand where to get needed data sets, when to request data, how to implement webhooks, when to update document statuses, and how to end-to-end test with trading partners. # Testing the Flow Logicbroker recommends using Postman for testing, as it lets you mimic API calls and view their response, before having write any code. Download postman [here](https://www.getpostman.com/apps) On the top of this page, you will see a button that says “Run in Postman”. Clicking this will open postman, and copy the entire collection (with folders) into your Postman application. (Note: It will have the name “Retailer Order Lifecycle”, but will include all necessary flows). Following each step will persist the data to the next step, showing you the ideal process for order processing. To begin the test, you will need to enter your stage API Key as a variable. You can do this by clicking the following icon and then "Edit" next to environments. Update the highlighted **subscription-key** variable with your API Key and click **save**. \*Note: all the variables listed are updated with test data as you go through the flow.\* **RetailerPartnerPO**, **TestSKU1**, **TestPartnerSKU1** , and **TestUPC1** are all defaulted with values, however they can be changed to simulate orders with real line items. For the Supplier Order Lifecycle variables will get generated automatically for creation of Acknowledgements, Shipments, and Invoices. These will be identified as **LogicbrokerKey**, **AckDetail**, **ShipDetail**, and **InvoiceDetail**. For the supplier flow you will only need to enter the subscription-key variable. # Additional Resources Here are some links to additional documentation that will help you with your integration. [API Reference](https://stage.commerceapi.io/swagger/ui/index) [Help Center](http://help.logicbroker.com/hc/en-us) [Document Standards](https://help.logicbroker.com/hc/en-us/categories/360001378711-Document-Standards)