TaskRabbit · OAuth Scopes

TaskRabbit OAuth Scopes

OAuth 2.0 derived

TaskRabbit 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://taskrabbit.auth0.com/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.

Gig EconomyHandymanHome ServicesMarketplaceDeliveryMovingPartner APIIKEA
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://taskrabbit.auth0.com/oauth/token
Flows
clientCredentials

Scopes (0)

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

TaskRabbit's gated Partner API authenticates via Auth0 machine-to-machine OAuth2 client-credentials tokens issued during partner onboarding, and its documentation (https://developer.taskrabbit.com/docs/getting-started) publishes no OAuth scopes or scope-based permissions.

📄 Provider scope reference: https://developer.taskrabbit.com/docs/getting-started

Source

OAuth Scopes

taskrabbit-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/taskrabbit-openapi.yml
docs: https://developer.taskrabbit.com/docs/getting-started
note: TaskRabbit's gated Partner API authenticates via Auth0 machine-to-machine OAuth2
  client-credentials tokens issued during partner onboarding, and its documentation
  (https://developer.taskrabbit.com/docs/getting-started) publishes no OAuth scopes
  or scope-based permissions.
schemes:
- name: oauth2
  source: openapi/taskrabbit-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://taskrabbit.auth0.com/oauth/token
  description: Auth0 machine-to-machine (M2M) OAuth2 client-credentials grant. Credentials are
    issued during partner onboarding.
scopes: []