User Questions: Cin7 Core API
Here are some user questions we have received and which may be of help in solving your issue. If you don't find a solution to your problem, do not hesitate to get in touch with Cin7 Core support for an answer.
Do I need to whitelist any Cin7 Core IP Addresses to allow connection with my servers or receive emails?
If you need to configure the host server(s) for your eCommerce stores or allow API clients to receive requests from Cin7 Core, or you are not receiving any emails from Cin7 Core, we recommend whitelisting the following Cin7 Core IP addresses:
We also recommend whitelisting the following Cin7 Core IP addresses:
Cin7 Core IP address: 23.96.51.98
Cin7 Core mail server IP address: 149.72.123.201
Cin7 Core front end address: 52.249.203.83
Integrations (for WooCommerce and Magento calls): 13.82.183.64
The whitelisting of the mail server IP address is particularly helpful in case you're not receiving any emails from Cin7 Core, which may have been dumped to your mail server's Spam folder all the while.
If you don't know how to go about whitelisting IP addresses, seek your hosting provider's support.
How do we use the API to pull/push orders from Cin7 Core to our system?
To get Cin7 Core orders into your system, you will have to send a POST request to subscribe to an event type (click for more information). The available event types are:
Sale/QuoteAuthorized
Sale/OrderAuthorized
Sale/Voided
Sale/Backordered
Sale/ShipmentAuthorized
Sale/InvoiceAuthorized
Sale/PickAuthorized
Sale/PackAuthorized
Sale/CreditNoteAuthorized
Sale/Undo
Sale/PartialPaymentReceived
Sale/FullPaymentReceived
Sale/ShipmentTrackingNumberChanged
Once an order reaches a specified event type you have subscribed to, a JSON payload will be sent to the endpoint you specified during the webhook subscription. Using the "SaleOrderNumber" in the JSON, make a GET request to retrieve any relevant information. Click here for more details.
Is there a way to query by date and get more recent purchase orders via the Cin7 Core API?
We are developing a couple of internal systems that will be using the Cin7 Core API and it seems that when I search using the UpdatedSince field and use today's date, it returns transaction with very old dates. Is there a way to query by date and get more recent purchase orders?
We recommend that you use webhooks, as these can return data when actions/events happen with your sales and purchases. You can find more information about webhooks here. Webhooks work through the Automation module in Cin7 Core. If you're not subscribed to the Automation module yet, you can try it out for 30 days, which would be enough time for you to check if it helps meet your requirements. For more information on adding the Automation module to your Cin7 Core subscription, click here.
How do we get the shipping address for the order using Cin7 Core API?
Sale (see https://dearinventory.docs.apiary.io/#reference/sale)
Sale/Fulfilment (see https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment)
Sale/Fulfilment/Ship (see https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment-ship)
Can Cin7 Core API identify the different order lines, when there are multiple items in an order?
Yes, Cin7 Core API can handle this scenario. The following sample code illustrates this (note the boxed lines):
We have a warehouse for fulfilling orders. When an order is placed in Cin7 Core, we get the order information using a webhook. Once we get the order, what are the next steps for sending order status to Cin7 Core, given we pick, pack and ship the order ourselves? Explain the steps in detail, together with the JSON and the API endpoints that will allow us to update the order status in Cin7 Core.
You will need to create or update existing fulfilments in Cin7 Core by supplying specific products picked, boxes and shipment details. Please find these three (3) API endpoints with sample requests in the documentation.
https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment
https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment-pick
https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment-pack
https://dearinventory.docs.apiary.io/#reference/sale/sale-fulfilment-ship
You can use the API explorer to test the payload and how it affects the sale.
If you would like to skip the details and just update the sales orders with shipped status, you can use the auto-pick parameter in the Pick endpoint.
How do we use the API to notify us when an order is cancelled? Can a buyer still cancel the order if it has been shipped already?
Order cancellation is known in Cin7 Core as Void or Undo. Orders can be undone or voided at any point in the order.
You can use the Sale/Voided and Sale/Undo events in Cin7 Core webhooks to be notified when an order is cancelled, and update your system using the SaleID in the payload. See https://dearinventory.docs.apiary.io/#reference/webhooks/webhooks for more information.
To be able to use webhooks, you should add the Automation module to your Cin7 Core subscription. See Adding Trials of the POS, B2B, API and Automation Modules to Paid Plans for more information. You can also get more details from Cin7 Customer Support.
How does Cin7 Core handle buyer returns and communicate these using the API?
All returns in Cin7 Core are processed as credit notes. For more information, see Customer Credit Notes and Refunds.
For more information on how the Cin7 Core API handles Purchase credit notes, see the links in our Cin7 Core API documentation below:
https://dearinventory.docs.apiary.io/#reference/purchase/purchase-credit-note
https://dearinventory.docs.apiary.io/#reference/purchase/advanced-purchase-credit-note.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB