Carriers API
List the curated carrier selector registry and understand how polling resolves exact provider codes across the complete bundled TrackingMore directory.
List Enabled Carriers
/api/v1/carriersThis public endpoint returns the curated carrier registry enabled in the deployed database and used by merchant selectors. The current production migration installs 49 rows. No bearer token is required. This endpoint is intentionally smaller than the complete upstream provider directory.
Carrier Codes
Persist and send the normalized OrderTrackify carrier code returned by the API rather than a display-name guess. OrderTrackify translates that internal code to the upstream provider's separate aggregator code when polling; clients should not guess or persist provider-specific codes. After a successful provider response, its shipment-specific confirmed code takes precedence on later polls, including regional codes outside the curated selector registry.
Full Provider Resolution
The bundled TrackingMore V4 snapshot contains 1,572 unique provider codes. Polling can validate an exact provider code or an unambiguous exact display name against that directory without exposing every provider as a selector row. Broad substring matching is not used because similarly named regional and service variants can route to different TrackingMore codes. When no trusted code exists, OrderTrackify asks TrackingMore to detect the courier before creating or retrieving the tracking, and a provider 4120 rejection permits one fresh detection-and-retry cycle.