Webhooks allow you to see status, carrier updates, and tracking events the moment they occur, not on a delay.

Using Public API end points allows you get the data you need when you need it.

Pull saved custom reports programmatically into your dashboards, data warehouses, or BI tools.

Polling vs. webhooks : choosing the right approach

Two patterns exist for staying up to date on shipment changes. Each has its place, but for most real-time use cases, webhooks are significantly more efficient

Webhooks

Register a URL endpoint and Tai TMS notifies you instantly when a shipment is updated. No repeated polling - you only receive data when something actually changes.

Shipment updated in Tai TMS → Tai sends POST to your endpoint → Your system processes event → Respond 200 OK

Characteristics

Instant notification on any shipment change
Minimal API usage - no wasted requests
Scales effortlessly with your shipment volume

Using Webhooks

You can view our example supported webhooks models Example Payloads and documentation in our Knowledge Base including how to register API keys.

Polling

Polling flow

Your system → GET /shipments (every N minutes) → API returns full payload → Diff for changes in your code

Characteristics

High request volume against your rate limit
Change detection is delayed by your polling interval
Easy to implement with no additional setup

Connecting to custom reports

Any report you've built and saved in the Tai TMS reporting interface can be accessed programmatically via the API — making it easy to pipe data into your BI tools, data warehouse, or internal dashboards.

How it works

Step 1 - Build and save your report
Create a custom report inside the Tai TMS portal using any filters, columns, and date ranges you need. Save it with a recognizable name.

Step 2 - Retrieve your report ID
Each saved report has a unique ID accessible from the report settings page, or by listing all reports via GET /reports.

Step 3 - Request report data
Call the reports endpoint with your report ID and desired date range. Responses are returned as paginated JSON, ready for ingestion.

Step 4 - Schedule or automate
Run report pulls on a cron schedule, trigger them via CI pipelines, or chain them with webhook events for fully automated data workflows.

How to get report data

Verified vendor program

Vendors who complete a technical verification process can have rate limits significantly increased or removed entirely for specific endpoints. Limits are tailored to your integration's actual usage profile.

Verification process:

Step 1 - Submit a verification request
Contact the Tai TMS integrations team with your use case, expected request volume, and endpoint requirements.

Step 2 - Technical review
The Tai team reviews your integration architecture to confirm it follows best practices — including webhook usage and error management.

Step 3 - Limit adjustment
Once verified, your API credentials are updated with a custom rate limit profile. Certain endpoints may be fully uncapped based on your use case.