The API Report CardAPI Index
Tai Software

Tai Software API

tai-software.com

A public REST API with a developer portal at docs.taicloud.net, webhooks, and published rate limits. Auth is a single x-api-key per customer with no OAuth, and keys arrive through LSP onboarding. The documented surface is shipment-centric; accounting and master data endpoints are thinner.

Last verified: July 2026Logistics & Supply Chain
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST API with a developer portal at docs.taicloud.net, webhooks, and published per-endpoint rate limits.
AccessPOORKeys are issued through the LSP Onboarding Guide, not self-serve, and production hosts are per-tenant site-code subdomains.
CoveragePOORShipping Service V2 is six shipment operations; accounting, carrier, and master data live behind separate, less-documented endpoints.
AuthPOORSingle x-api-key header bound to one customer; no OAuth 2.0, so rotation and per-user scoping are coarse.
Docs & DXGOODDeveloper portal at docs.taicloud.net includes an llms.txt index, webhook docs, and published rate limits; no official SDKs.
StabilityMIXEDV1 stays documented for legacy clients alongside V2, but customers report unannounced changes hitting integrations.
Supergood: Tai Software has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Tai Software scores D on the API Report Card. A public REST API with a developer portal at docs.taicloud.net, webhooks, and published rate limits. Auth is a single x-api-key per customer with no OAuth, and keys arrive through LSP onboarding. The documented surface is shipment-centric; accounting and master data endpoints are thinner.

Tried to integrate with Tai Software?
SOURCES
Auth is API-key only (`x-api-key`) - no OAuth 2.0, so credential rotation and per-user scoping are coarse vs Rose Rocket / Samsara learn.tai-software.com β†—
Production base URL is per-tenant (`[site-code].taicloud.net`) - integrators must discover and configure the site-code per customer; can't hit a single global host learn.tai-software.com β†—
API access requires onboarding via the **LSP Onboarding Guide** - no self-serve sandbox like Stripe/Plaid; sample requests/responses are shared on request learn.tai-software.com β†—
Endpoint surface is shipment-centric (book/get/track/alerts/refs) - other operating data (accounting, carrier records, master data) lives behind separate, less-documented endpoints docs.taicloud.net β†—
Two parallel doc surfaces - `docs.taicloud.net` (developer portal w/ OpenAPI) and `learn.tai-software.com` (knowledge base) - create confusion about the canonical reference learn.tai-software.com β†—
Customer reviews mention 'unannounced changes' to the product which can impact integration stability capterra.com β†—
No public status page / uptime SLA published on the developer portal docs.taicloud.net β†—
'Frequent bugs, unannounced changes, lack of compliance awareness and quality control' reported by some customers capterra.com β†—
'Training is subpar and outsourced overseas' - users say they cannot make rate confirmations in a timely manner after onboarding capterra.com β†—
'Tai will string you along and even if it's determined their TMS will not work for your company, they will still charge you for months' capterra.com β†—
Support response times - 'it took a while to get responses to some issues, and getting someone on the phone is difficult' capterra.com β†—
UI/UX feedback that the system 'isn't laid out well' and 'designers don't appear familiar with the broker role' capterra.com β†—
No public pricing - quoted per-user/per-module after a sales call capterra.com β†—
Brand/entity confusion between **Tai Software** (Huntington Beach, Walter Mitchell CEO) and **Teknowlogi** (Kennesaw GA, Spencer Askew CEO) - the original 2005 parent still surfaces in Capterra/SoftwareAdvice listings as 'Teknowlogi TAI TMS' softwareadvice.com β†—