Blacksmith · OAuth Scopes
Blacksmith OAuth Scopes
OAuth 2.0
derived
Blacksmith 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://github.com/login/oauth/access_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.
CI/CDGitHub ActionsRunnersCachingDocker
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://github.com/apps/blacksmith
https://github.com/apps/blacksmith
Token URL
https://github.com/login/oauth/access_token
https://github.com/login/oauth/access_token
Flows
authorizationCode
authorizationCode
Scopes (0)
Blacksmith 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.
Blacksmith publishes no OAuth scopes - login is exclusively GitHub SSO via the Blacksmith GitHub App, and dashboard access is role-based, inherited directly from GitHub organization/repository permissions rather than granted through scopes (https://docs.blacksmith.sh/blacksmith-administration/permissions).
Blacksmith publishes no OAuth scopes - login is exclusively GitHub SSO via the Blacksmith GitHub App, and dashboard access is role-based, inherited directly from GitHub organization/repository permissions rather than granted through scopes (https://docs.blacksmith.sh/blacksmith-administration/permissions).
📄 Provider scope reference: https://docs.blacksmith.sh/blacksmith-administration/permissions