Langflow · OAuth Scopes
Langflow OAuth Scopes
OAuth 2.0
derived
Langflow 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 api/v1/login.
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.
AIArtificial IntelligenceAgentsWorkflowsLow-CodeVisual BuilderLangChainRAGMCPOpen SourceFastAPI
Scopes: 0
Flows: password
Method: derived
OAuth endpoints
Token URL
api/v1/login
api/v1/login
Flows
password
password
Scopes (0)
Langflow 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.
Langflow does not publish OAuth scopes — API access is authorized via API keys that adopt the privileges of the creating user (superuser vs regular user roles), not scope-based permissions (https://docs.langflow.org/api-keys-and-authentication).
Langflow does not publish OAuth scopes — API access is authorized via API keys that adopt the privileges of the creating user (superuser vs regular user roles), not scope-based permissions (https://docs.langflow.org/api-keys-and-authentication).
📄 Provider scope reference: https://docs.langflow.org/api-keys-and-authentication