Integrations · Tracking and visibility
project44 integration: load tracking in Tezify
Create a client application in project44 Movement, paste its Client ID and secret into the project44 card, save and test. Brokers then press Start tracking with project44 on a load. Carriers turn on Share with project44.
What project44 does in Tezify
Brokerage side: on a brokered load, press Start tracking with project44. project44 tracks the carrier through its ELD or the driver's phone. Positions, stop arrivals and ETAs land on the load and its check calls.
Carrier side: on one of your own loads, turn on Share with project44. Your truck's ELD position goes to the broker's project44 every 30 minutes, so the broker stops calling for updates.
Each company uses its own project44 account and its own keys.
Who needs it
Both carriers and brokers. In a workspace with a separate brokerage company (set on Company profile), each company enters its own project44 keys, and work on a load uses the keys of the company that load belongs to. With one company, there is one set of keys.
What you need from project44
- A project44 Movement account.
- A Customer Admin login there, to create a client application.
- For instant updates, your project44 rep to set up a webhook (optional).
Connect project44 to Tezify
- Sign in to project44 Movement as a Customer Admin.
- Open Settings, then Client applications, and create a client application named Tezify.
- In Tezify, open Integrations and find the project44 card. The link at the top of this page opens it.
- Copy the Client ID into Client ID and the secret into Client secret. project44 shows the secret only once.
- If your account is in Europe or is a sandbox, pick it in Region. Leave it blank for North America.
- Optional, for instant updates: type a long random string into Webhook key (optional). Ask your project44 rep to send webhooks to your Tezify address /api/webhooks/project44?tenant=your account, with the header x-tezify-key set to that same string.
- Tick Active and press Save keys.
Test the connection
Press Test connection. Tezify asks project44 for an access token with your Client ID and secret. If project44 issues one, the card turns Connected. If your webhook key is shorter than 24 characters, the result tells you to make it longer.
Common errors and fixes
| What you see | What to do |
|---|---|
| project44 refused the client ID or secret. | Create a new client application and paste both values again. Check the Region matches your account. |
| Too many requests (429). | project44 allows 5 token calls a minute per client. Wait a minute and test again. |
| Updates arrive only every 30 minutes. | The webhook is not set. Give your project44 rep the webhook address and the same Webhook key. |
What syncs and how often
- Brokerage: positions, stop arrivals and ETAs, by webhook the moment project44 has them, and a refresh every 30 minutes either way.
- Carrier: your newest ELD position is sent to project44 every 30 minutes for each load you share.
Limits
- Carrier sharing needs an ELD connected in Tezify, because it sends the ELD position.
- Access mode is Read-only or Full control. Full control is the default, because starting tracking writes a shipment to project44.
- project44 allows 5 token calls a minute.
Ready to do it? This lives at /admin/integrations?open=project44 in Tezify.