Skip to main content
TruckerFetch authenticates REST with an API key and hosted MCP with an OAuth grant. Both use the current permissions and active Pro entitlement of the owning account.

​
REST API keys

Create, rotate and revoke purpose-specific keys in API keys. Pass your secret over HTTPS in the bearer header:
Browser sign-in does not authenticate data API requests. Use a key with only the scopes your application needs. A key does not grant another account’s watchlists, exports or historical access. Keep keys in a secret manager or protected environment variable. Do not place them in query strings, a repository, webhook URLs, telemetry or assistant messages. Rotate a leaked key and revoke the old credential from the dashboard.

​
Hosted MCP OAuth

Add https://truckerfetch.com/api/mcp to a compatible remote MCP client and follow its OAuth sign-in flow. Review the requested permissions on the TruckerFetch consent screen. An API key is not a hosted MCP OAuth token. Review and revoke assistant connections in Connections. If an operation requests another scope, review the authorization prompt before retrying.

​
Authentication failures

A downgrade or revocation can invalidate access after a successful request. Check current access again when resuming a job or download.