Capgo · Authentication Profile

Capgo App Authentication

Authentication

Capgo secures its APIs with apiKey, http, and oauth2 across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyArtificial IntelligenceMobileDevelopmentCapacitor
Methods: apiKey, http, oauth2 Schemes: 4 OAuth flows: authorizationCode API key in: header

Security Schemes

CapgoApiKeyAuth apiKey
· in: header (x-api-key)
CapgoBearerAuth http
scheme: bearer
CapgoOAuth oauth2
· flows: authorizationCode
CapgoLegacyAuthorization apiKey
· in: header (authorization)

Source

Authentication Profile

Raw ↑
generated: '2026-11-04'
method: derived
source: openapi/capgo-app-openapi.json
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: CapgoApiKeyAuth
  type: apiKey
  in: header
  parameter: x-api-key
  description: Send the raw Capgo API key in the `x-api-key` header. Generate or rotate keys
    at https://console.capgo.app/settings/organization/api-keys.
  sources:
  - openapi/capgo-app-openapi.json
- name: CapgoBearerAuth
  type: http
  scheme: bearer
  bearerFormat: Capgo API key
  description: 'Send a Capgo API key, or an access token from the Capgo OAuth flow, as `Authorization:
    Bearer <key>`.'
  sources:
  - openapi/capgo-app-openapi.json
- name: CapgoOAuth
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.capgo.app/mcp/oauth/authorize
    tokenUrl: https://api.capgo.app/mcp/oauth/token
    scopes: 1
  description: 'OAuth 2.0 authorization code flow with PKCE (S256) and dynamic client registration
    (https://api.capgo.app/mcp/oauth/register). Issuer: https://capgo.app. The access token
    is a Capgo API key limited to the organizations the user selects on the consent screen;
    send it as a Bearer token.'
  sources:
  - openapi/capgo-app-openapi.json
- name: CapgoLegacyAuthorization
  type: apiKey
  in: header
  parameter: authorization
  description: Legacy raw API key in the `authorization` header without a Bearer prefix. Prefer
    `x-api-key`.
  sources:
  - openapi/capgo-app-openapi.json

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/capgo-app-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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