null

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Our API services are best used when your system is capable of integrating via web calls using REST.

Typical System Process for Create Consignment

image-20240919-001351.png

Further Information

Detailed Flow Chart To Use Our

Systems that can integrate with API:

  • Transport Management System (TMS) that is already capable of consignment creation and label printing. You can leverage off OneFlo’s functionality on quoting based on your efm Contract Rate Card.

  • Warehouse Management System (WMS) that is responsible for stock keeping and wants to integrate with OneFlo’s quoting function to determine least cost freight options.

  • Enterprise Resource Planning (ERP) for retrieving indicative pricing information for freight in relation to Order data.

  • Shopping Carts and Point-of-Sale Systems (POS) for presenting options for end customers to determine pricing upon checkout.

Our API follows a RESTful API Architecture.

A RESTful API -- also referred to as a RESTful web service or REST API -- is based on representational state transfer (REST), which is an architectural style and approach to communications often used in web services development.

REST technology is generally preferred over other similar technologies. This tends to be the case because REST uses less bandwidth, making it more suitable for efficient internet usage. RESTful APIs can also be built with programming languages such as JavaScript or Python.

  • No labels