Deoochform · OAuth Scopes
Deoochform OAuth Scopes
OAuth 2.0
none
Deoochform 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.
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.
CompanyFormsForm BuilderSurveysArtificial IntelligenceMCPPaymentsWebhookNo-Code
Scopes: 0
Flows:
Method: none
Scopes (0)
Deoochform 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.
The OAuth 2.0 docs describe no scope parameter or scope list. Every token is scoped to the account that owns it ("Every endpoint below is scoped to the account that owns the token"). The four Slack permissions on /help/slack (commands, chat:write, im:history, im:write) are Slack's scopes for the Deoochform Slack app, not Deoochform API scopes.
The OAuth 2.0 docs describe no scope parameter or scope list. Every token is scoped to the account that owns it ("Every endpoint below is scoped to the account that owns the token"). The four Slack permissions on /help/slack (commands, chat:write, im:history, im:write) are Slack's scopes for the Deoochform Slack app, not Deoochform API scopes.
📄 Provider scope reference: https://deoochform.com/help/api
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.