Integrations · Tracking and visibility
MacroPoint integration: track brokered loads in Tezify
Get an API username, password and Partner MPID from Descartes MacroPoint, enter them with a callback token on the MacroPoint card, then set the four callback URLs in MacroPoint Company Preferences.
What MacroPoint does in Tezify
On a brokered load, press Start tracking with MacroPoint. MacroPoint texts the carrier's driver, or tracks the carrier's ELD, and sends locations, stop arrivals, departures and late alerts back to the load and its check calls.
Stop tracking ends it. Tracking runs until 12 hours past the last appointment, up to your contracted maximum.
Who needs it
Freight brokers. The MacroPoint card shows on the brokerage company's Integrations page only, because it is about outside carriers or broker pricing.
What you need from MacroPoint
- A Descartes MacroPoint account with API access.
- An API username and password. These are not your website login.
- Your Partner MPID, and your contracted tracking interval and length.
Connect MacroPoint to Tezify
- Ask Descartes MacroPoint for an API username and password, your Partner MPID, and your contracted tracking interval and length.
- In Tezify, open Integrations and find the MacroPoint tracking card. The link at the top of this page opens it.
- Fill in API username, API password and Partner MPID.
- Make up a long random string of 24 or more characters and put it in Callback token.
- Optional: fill in Update every (minutes) and Longest tracking (hours) from your contract. Blank means 15 minutes and 72 hours.
- Tick Active and press Save keys.
- In MacroPoint Company Preferences, set the Location, Trip Event, Order Status and Schedule Alert callback URLs to your Tezify address /api/webhooks/macropoint?tenant=your account&token=your callback token.
Test the connection
Press Test connection. Tezify signs in to MacroPoint without creating anything. If the callback token is short, the result says so. Then start tracking on one load and watch the first location arrive.
Common errors and fixes
| What you see | What to do |
|---|---|
| MacroPoint refused the login. | Check the API username and password. They are not your MacroPoint website login. |
| Locations never arrive. | The callback URLs in MacroPoint must carry the same callback token as the card. |
| The callback token is short. | Use 24 or more random characters so nobody can guess it. |
What syncs and how often
- MacroPoint pushes each update to Tezify as it happens: location, trip events, order status and schedule alerts.
- MacroPoint has no position read, so there is no 30-minute refresh. If the callbacks are not set, nothing arrives.
Limits
- Brokerage side only. Carriers answer MacroPoint requests in the MacroPoint app.
- MacroPoint needs the carrier's DOT number on the order.
- Interval and tracking length are set by your MacroPoint contract.
Ready to do it? This lives at /admin/integrations?open=macropoint in Tezify.