Tekmetric · OAuth Scopes

Tekmetric OAuth Scopes

OAuth 2.0 derived

Tekmetric 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.

Tokens are issued from https://shop.tekmetric.com/api/v1/oauth/token.

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.

AutomotiveAuto RepairShop ManagementFleetVertical SaaS
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://shop.tekmetric.com/api/v1/oauth/token
Flows
clientCredentials

Scopes (0)

Tekmetric 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.

Tekmetric does not publish OAuth permission scopes - the API uses an OAuth 2.0 client credentials grant behind a partner approval gate (https://api.tekmetric.com), and the token response's scope field carries the space-separated Shop IDs the client is authorized for rather than permission scopes.

📄 Provider scope reference: https://api.tekmetric.com

Source

OAuth Scopes

tekmetric-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/tekmetric-openapi.yml
schemes:
- name: oauth2
  source: openapi/tekmetric-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://shop.tekmetric.com/api/v1/oauth/token
  description: OAuth 2.0 client credentials grant. Requires an approved Client ID/Secret issued
    by Tekmetric after a manual request-access review (reported at roughly 2-3 weeks).
docs: https://api.tekmetric.com
note: Tekmetric does not publish OAuth permission scopes - the API uses an OAuth 2.0
  client credentials grant behind a partner approval gate (https://api.tekmetric.com),
  and the token response's scope field carries the space-separated Shop IDs the client
  is authorized for rather than permission scopes.
scopes: []