Required Callback Endpoints for Track & Trace

To receive structured updates from Augment's Track & Trace workflow, you must implement and subscribe to the following four callback endpoints. When Augie obtains information during the tracking workflow, it pushes updates to your system via these endpoints.

All updates are outbound from Augment to the brokerage's TMS. Your system must expose each endpoint, return a 200 status on success, and handle the payloads described below.

Note: Augment sends all relevant events for loads being tracked — your system should filter or route based on load number, event type, or other criteria as needed.

Endpoint	When it fires
Stop Update	Augie captures a stop milestone (arrival, departure, etc.)
Tracking Event	Augie obtains an ETA, location, or in-transit status update
Load Carrier Event	Carrier contact or driver information changes
Comment	A communication (call, email, text) yields no structured update

Getting Started

1. Implement the four callback endpoints in your TMS according to the schemas above.
2. Provide your endpoint URLs to the Augment team.
3. Specify your authentication method — Augment supports multiple auth types for callback delivery.
4. Test — work with your Augment CS contact to send test callbacks and verify payloads are received and processed correctly.

Common Issues

• Timeouts: Augment retries failed deliveries with exponential backoff (up to 3 retries). If your endpoint is slow to respond, ensure it returns 200 promptly and processes asynchronously if needed.
• Duplicate events: Design your handlers to be idempotent. Retries may result in the same event being delivered more than once.

Questions?

Reach out to your CS contact for help setting up or testing your callback subscriptions.