GitHub Actions · Authentication Profile

Github Actions Authentication

Authentication

GitHub Actions secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer
personalAccessToken http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api
docs: https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api
summary:
  types:
  - http
  http_schemes:
  - bearer
  token_types:
  - fine-grained-pat
  - classic-pat
  - oauth-user-token
  - github-app-installation-token
  - github-actions-job-token
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    Authorization: Bearer <token>. Accepts a fine-grained or classic personal
    access token, an OAuth user-to-server token, a GitHub App installation
    access token, or the automatic GITHUB_TOKEN inside a workflow run.
  sources:
  - openapi/github-actions-openapi.yml
- name: personalAccessToken
  type: http
  scheme: bearer
  description: Fine-grained personal access token scoped with Actions permissions.
  sources:
  - openapi/github-actions-openapi.yml
notes:
  - Access is governed by classic OAuth scopes or fine-grained token/App permissions; see scopes/github-actions-scopes.yml.
  - Basic auth with username + PAT is deprecated; bearer-token auth is required.
  - GITHUB_TOKEN permissions inside a workflow are declared via the workflow `permissions:` block.