OneFlo offers an ability to send order data directly which will be used for Order Lookup in the consigning screen.
| Table of Contents | ||
|---|---|---|
|
When to use this?
You can use this option if the following conditions are satisfied:
If your environment does not allow an external software installed on it (eg for security reasons).
If your ERP (order management system) is capable of utilising a RESTful web service.
Your If your ERP (order management system) must adhere to the Order Lookup - Information Requirements and Sample Files or can provide a JSON payload as defined in the API documentation (see link below under Technical Details) https://uat-apidocs.flipgroup.com.au/
| Note |
|---|
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:
|
Requirements
...
Please reach out to your Account Manager or IT Implementation Consultant for the following information:
OneFlo Account Id (6-digit)
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
...
| Expand | ||
|---|---|---|
| ||
Function: OrderLookup
...
API Web Services
To learn more about our API, please see API Web Services
More Information
| Child pages (Children Display) | ||
|---|---|---|
|