The 3GTMS integration has two data flows:
3GTMS → Chain: 3GTMS exports load updates to Chain (XML export)
Chain → 3GTMS: Chain sends XML updates back to 3GTMS
This doc covers #1.
3GTMS → Chain (Load exports to Chain)
This flow is how 3GTMS sends data to Chain. Chain is already fully mapped to 3GTMS’s standard Load XML export, so the main setup step is enabling exports to Chain’s endpoint. You will need to request this from your 3GTMS technical representative who handles configuring exports.
From a 3G technical perspective, this involves setting up Saved Searches with Process Automations (PAs) to export out the entire load object (as-is) to the endpoints below.
What you need to request from 3GTMS
Ask 3GTMS to enable XML exports to Chain’s URL when any of the following events occur:
Load status changes - any time the status of the load changes
Carrier added or removed - any time a carrier is added or removed on a load
Driver / truck / trailer information updated
Stop appointment changes
Export destination (Endpoint URLs)
Production
URL:
https://api.chaineapp.com/apps/events/v1/3gtms
Staging
URL:
https://api.staging.chaineapp.com/apps/events/v1/3gtms
Required headers (Authentication)
3GTMS must include an authentication token in the request header:
Header name:
AuthenticationHeader value: Token generated in Chain
Go to: Workspace → Settings → Apps → 3GTMS
Generate/copy the token and provide it to 3GTMS
Note: Staging and Production use different environments and may use different tokens. Use the token generated in the corresponding Chain environment.