The API Report CardAPI Index
Track-POD

Track-POD API

Last-mile delivery management & electronic proof of delivery (ePOD) SaaS · track-pod.com

A free public REST API (JSON and XML) documented at api.track-pod.com, with self-generated keys, webhooks for order and route events, and a published 20 req/s limit. Auth is API-key only, no OAuth. There is no OpenAPI spec or official SDK; the reference is static HTML.

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

SCORECARD

ExistenceGOODFree public REST API in JSON and XML with full CRUD on orders, routes, drivers, and vehicles; reference at api.track-pod.com.
AccessGOODKeys are self generated in Settings and the API is free, with per-client keys, IP whitelisting, and per-method scoping.
CoverageGOODFull CRUD on orders, routes, drivers, addresses, and vehicles, plus webhooks for order and route lifecycle events.
AuthPOORAPI-key-only auth; no OAuth 2.0 or SSO, so third-party scoping and rotation stay manual per key.
Docs & DXPOORNo OpenAPI spec or official SDKs; the reference is static HTML and webhook retry and signing semantics are thin.
StabilityMIXED
Supergood: Track-POD has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Track-POD scores D+ on the API Report Card. A free public REST API (JSON and XML) documented at api.track-pod.com, with self-generated keys, webhooks for order and route events, and a published 20 req/s limit. Auth is API-key only, no OAuth. There is no OpenAPI spec or official SDK; the reference is static HTML.

Tried to integrate with Track-POD?
SOURCES
Only **API-key auth** supported - no OAuth 2.0, no SSO, no app-builder flow for third-party developers track-pod.freshdesk.com
**20 req/s / 400 req/min** is a hard per-key ceiling - large back-fills, bulk imports, and multi-tenant integrators must throttle and batch track-pod.com
**No official SDKs** - integrators rely on raw HTTP or community efforts (e.g., Onetoweb PHP) github.com
**No published OpenAPI/Swagger spec, no llms.txt** - AI agents and codegen pipelines must scrape the static HTML reference at api.track-pod.com/index.html api.track-pod.com
Webhook delivery semantics (retry behavior, signing/HMAC verification, ordering guarantees, replay handling) are sparsely documented compared to peers track-pod.freshdesk.com
Native ERP integration set is narrow (Shopify, eBay, Xero, QuickBooks) - everything else (NetSuite, SAP, Oracle, MS Dynamics, WooCommerce, Magento, Salesforce) routes through Zapier or custom API work track-pod.com
Documentation is split between api.track-pod.com (reference), the marketing site (overview), and Freshdesk (how-tos), forcing integrators to hunt across three properties track-pod.freshdesk.com
API supports both JSON and XML payloads - extra surface area means more test matrix and content-type negotiation bugs for integrators track-pod.com
Dispatcher web UI is described as dated and cluttered when handling multiple concurrent tasks elogii.com
Mobile apps reported as glitchy with a meaningful feature/quality gap between Android and iOS versions elogii.com
Pricing perceived as on the higher side, especially per-order tier step-ups ($285 for 1,500 tasks then $0.19/task) capterra.com
Refund policy frustrations reported after subscription dissatisfaction elogii.com
Route auto-optimization isn't always accurate and frequently requires manual driver/route overrides elogii.com
Traffic predictions reported as unreliable in dense urban areas, degrading ETA accuracy elogii.com
Two pricing models (per-driver vs per-order) create migration friction as order volume scales track-pod.com
Native integration set is narrow (Shopify, eBay, Xero, QuickBooks) - everything else routes through Zapier or custom API work track-pod.com