Order Lookup - RESTful (API) Method

Owned by Dennis Navarro
Last updated: Jul 17, 2024
1 min read

OneFlo offers an ability to send order data directly which will be used for Order Lookup in the consigning screen.

 

When to use this?

You can use this option if the following conditions are satisfied:

  1. If your environment does not allow an external software installed on it (eg for security reasons).

  2. If your ERP (order management system) is capable of utilising a RESTful web service.

  3. If your ERP (order management system) can provide a JSON payload as defined in the API documentation https://uat-apidocs.flipgroup.com.au/

    image-20240228-032142.png

     

If you choose to use RESTful API to send your orders, we won’t be able to do further pre-processing on your order data, therefore you must adhere to the OneFlo data requirements as per point 3 above.

The following are components where you may need to have a mapping in your system:

  1. OneFlo Account ID mapped to your warehouse locations or addresses

  2. Cost Centre Codes and Descriptions

  3. Carrier Service Codes when you choose to make a service decision within your business process

 

Requirements

Please reach out to your Account Manager or IT Implementation Consultant for the following information:

  1. OneFlo Account Id (6-digit)

  2. API Key

Technical Details

UAT Swagger: https://uat-apidocs.flipgroup.com.au/

Function: OrderLookup

Endpoint: https://api.flipgroup.com.au/customers/{accountId}/orderlookup

 

Production Swagger

https://apidocs.flipgroup.com.au/

 

API Web Services

To learn more about our API, please see API Web Servicesarchived

 

More Information