ERPNext · OAuth Scopes

ERPNext OAuth Scopes

OAuth 2.0 derived

ERPNext publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the ERPNext API on a user’s behalf.

Tokens are issued from /method/frappe.integrations.oauth2.get_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.

ERPEnterprise Resource PlanningAccountingInventoryManufacturingSalesCRMHROpen Source

Scopes: 1 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
/method/frappe.integrations.oauth2.authorize

Token URL
/method/frappe.integrations.oauth2.get_token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
all	Same permissions as the user who created the oAuth client	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/openapi.yaml
schemes:
- name: oAuth2
  source: openapi/openapi.yaml
  flows:
  - flow: authorizationCode
    authorizationUrl: /method/frappe.integrations.oauth2.authorize
    tokenUrl: /method/frappe.integrations.oauth2.get_token
  description: "This API uses OAuth 2 with the authorization code flow. \n[More info]https://frappe.io/docs/user/en/guides/integration/using_oauth)"
scopes:
- scope: all
  description: Same permissions as the user who created the oAuth client
  flows:
  - authorizationCode
  sources:
  - openapi/openapi.yaml