TheCarApi · OAuth Scopes
TheCarApi OAuth Scopes
OAuth 2.0
searched
TheCarApi uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
AutomotiveVehicle DataCar AuctionsUsed CarsVehicle InventoryClassifiedsMarket IntelligencePricingVINImage CDNEuropeKoreaJapan Auctions
Scopes: 0
Flows:
Method: searched
Scopes (0)
TheCarApi implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
TheCarApi publishes a real, named scope reference, but the scopes are attached to an API key rather than issued through an OAuth2 authorization flow. There are no oauth2 securitySchemes in the OpenAPI and no authorization/token endpoints. Scopes are granted per endpoint by the operator; a request to a route the key does not cover returns 403.
TheCarApi publishes a real, named scope reference, but the scopes are attached to an API key rather than issued through an OAuth2 authorization flow. There are no oauth2 securitySchemes in the OpenAPI and no authorization/token endpoints. Scopes are granted per endpoint by the operator; a request to a route the key does not cover returns 403.
📄 Provider scope reference: https://thecarapi.com/docs/authentication
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.