This page contains information on how to integrate your In-house TMS with Chain.
We make integrating with your TMS simple. Most TMS's have an export functionality where the entire load object can be exported as-is any time there is a change to the load. This is the preferred method of integration.
We recommend that you send the entire load object with all the fields to this end-point. Our workflow automation features can be created on any field in your TMS, and which will give your users an unlimited amount of possibilities when creating workflow rules. Chain will map your entire load object with all the fields to our internal load object and update the load accordingly in our system. This functionality allows customers to utilize the complete suite of features.
The flow is:
A load is created, updated, or deleted in your TMS
The entire load object with all the fields is exported to Chain via a webhook you provide. For deletion, you can send the unique load ID andthe action type of delete.
Events are then published back to a webhook you specify (depending on the functionality that is determined to be updated back in the TMS for the integration).
API Documentation
Please refer to the API Docs here:
The main steps are:
Create an API Key in Settings > Developers > Create API Key
You will make POST requests to https://api.chaineapp.com/apps/events/v1/api/shipment
In the Authorization header, please include the API Key you created in the first bullet point above.
Set the Content-Type header to application/json or application/xml, depending on how you did the mapping.
Map your TMS's load object to Chain's Load Object. Refer to schema here.
Every time there is any change on your load or stop, use the mapping you created and send the entire mapped load object with stops to our endpoint mentioned above
For example, in your TMS, if you remove the driver phone, this should trigger an API request to our standard load object (fully mapped, but you'll be missing the
How-to Video