Gitea · OAuth Scopes

Gitea OAuth Scopes

OAuth 2.0 searched

Gitea 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.

GitSource ControlDevOpsCI/CDCode HostingOpen-SourceSelf-HostedPackage RegistryIssue TrackingPull Requests
Scopes: 0 Flows: Method: searched

Scopes (0)

Gitea 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.

Gitea exposes two distinct scope systems. (1) OAuth2 / OpenID Connect provider scopes returned in the live openid-configuration. (2) Personal Access Token (PAT) permission scopes, formatted :, plus a special `all` scope. The Swagger 2.0 spec declares only apiKey/basic securityDefinitions (no oauth2 flow object), so these scopes are documented rather than derivable from the spec.

📄 Provider scope reference: https://docs.gitea.com/development/oauth2-provider

Source

OAuth Scopes

Raw ↑ 
generated: '2026-06-20'
method: searched
source: well-known/gitea-openid-configuration.json
docs: https://docs.gitea.com/development/oauth2-provider
note: >-
  Gitea exposes two distinct scope systems. (1) OAuth2 / OpenID Connect provider
  scopes returned in the live openid-configuration. (2) Personal Access Token
  (PAT) permission scopes, formatted <read|write>:<category>, plus a special
  `all` scope. The Swagger 2.0 spec declares only apiKey/basic securityDefinitions
  (no oauth2 flow object), so these scopes are documented rather than derivable
  from the spec.
schemes:
  - name: OpenIDConnect
    type: openIdConnect
    issuer: https://gitea.com
    authorizationUrl: https://gitea.com/login/oauth/authorize
    tokenUrl: https://gitea.com/login/oauth/access_token
    userinfoUrl: https://gitea.com/login/oauth/userinfo
    introspectionUrl: https://gitea.com/login/oauth/introspect
    jwksUri: https://gitea.com/login/oauth/keys
    grantTypes: [authorization_code, refresh_token]
    pkce: [plain, S256]
    source: well-known/gitea-openid-configuration.json
oidc_scopes:
  - scope: openid
    description: OpenID Connect authentication; issue an ID token.
  - scope: profile
    description: Access to the user's profile claims (name, preferred_username, picture, website, locale).
  - scope: email
    description: Access to the user's email and email_verified claims.
  - scope: groups
    description: Access to the user's group membership claim.
pat_scope_categories:
  note: >-
    Each category is grantable at read or write level, e.g. read:repository,
    write:issue. The `all` scope grants read+write across every category.
  levels: [read, write]
  categories:
    - activitypub
    - admin
    - issue
    - misc
    - notification
    - organization
    - package
    - repository
    - user
  special:
    - scope: all
      description: Grants both read and write permission across all categories.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/gitea-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.