Skribble · OAuth Scopes
Skribble OAuth Scopes
OAuth 2.0
none
Skribble 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.
CompanyE-SignatureDigital SignatureQualified Electronic SignatureSignature ValidationeIDASSwitzerland
Scopes: 0
Flows:
Method: none
Scopes (0)
Skribble 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.
Skribble uses API key authentication with JWT bearer tokens, not OAuth scopes. Authentication is documented at https://api.docs.skribble.com/authentication
Skribble uses API key authentication with JWT bearer tokens, not OAuth scopes. Authentication is documented at https://api.docs.skribble.com/authentication
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.