TheFork · OAuth Scopes
TheFork OAuth Scopes
OAuth 2.0
derived
TheFork 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://auth.thefork.io/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.
RestaurantReservationsBookingDiningPoint Of SaleMarketplace
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://auth.thefork.io/oauth/token
https://auth.thefork.io/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
TheFork 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.
TheFork does not use or document OAuth scopes; access is granted via an Auth0 client credentials flow (client_id/client_secret exchanged for a bearer token), with POS/Partners access controlled by API keys rather than scopes (https://docs.thefork.io/B2B-API/authentication).
TheFork does not use or document OAuth scopes; access is granted via an Auth0 client credentials flow (client_id/client_secret exchanged for a bearer token), with POS/Partners access controlled by API keys rather than scopes (https://docs.thefork.io/B2B-API/authentication).
📄 Provider scope reference: https://docs.thefork.io/B2B-API/authentication