Make a REST request
From your Pro workspace, create a scoped key. Set TRUCKERFETCH_ORIGIN to the HTTPS site origin and load your key into TRUCKERFETCH_API_KEY in your environment. Start with edition metadata.
curl --fail-with-body "$TRUCKERFETCH_ORIGIN/api/v1/editions/latest" \
-H "Authorization: Bearer $TRUCKERFETCH_API_KEY"Search the catalog
curl --fail-with-body "$TRUCKERFETCH_ORIGIN/api/v1/carriers/search" \
-H "Authorization: Bearer $TRUCKERFETCH_API_KEY" \
-H "Content-Type: application/json" \
--data '{"filters":{"states":["TX"],"fleet":{"min":1,"max":10}},"limit":20}'Follow the response’s opaque next cursor using the same filters. An empty publication is a valid result. The initial baseline may exist before the first daily edition. Add contact scope only when your integration needs reported contact fields.
Limits and errors
REST and MCP share account limits. Respect the retry interval on a 429 response. A 401 requires a valid credential. A 402 means the account lacks the required plan, and a 403 can indicate insufficient scope or archive access. Reauthorize after a revoked OAuth grant and replace expired REST keys in the dashboard.