AirOps · Authentication Profile

Airops Authentication

Authentication

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

CompanyApplicationArtificial IntelligenceContentSEOAEOAnswer Engine OptimizationGenerative Engine OptimizationWorkflowsMCPAnalyticsAgent SkillsOpenAPIKnowledge BaseContent MarketingCitations
Methods: http, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

apiKeyBearer http
scheme: bearer
oauth2 oauth2
scheme: authorizationCode · flows: authorizationCode

Source

Authentication Profile

Raw ↑
generated: '2026-08-13'
method: searched
source: https://docs.airops.com/api-reference/using-the-api/authentication
docs: https://docs.airops.com/api-reference/using-the-api/authentication
also_derived_from: openapi/airops-api-openapi.yml
spec_confirmation: >-
  Confirmed 2026-08-13 against the published OpenAPI harvested from
  https://api.airops.com/public_api/openapi.yaml. The spec declares exactly one
  security scheme — components.securitySchemes.bearer (type: http, scheme:
  bearer) — applied per-operation, with a 401 "Authentication error" response on
  all 42 operations. There is no document-level `security` default (flagged in
  overlays/airops-api-overlay.yaml). The OpenAPI does NOT model the OAuth 2.0
  scheme below: OAuth exists only for the hosted MCP server and is discoverable
  solely through the /.well-known/ documents, so the two auth surfaces are
  documented in different places and only this artifact unifies them.
summary:
  types: [http, oauth2]
  api_key_in: [header]
  http_schemes: [bearer]
  oauth2_flows: [authorizationCode]
schemes:
- name: apiKeyBearer
  type: http
  scheme: bearer
  location: header
  header: Authorization
  format: 'Bearer [example key]'
  description: >-
    Workspace API key presented as a Bearer token in the Authorization header for
    the REST API at api.airops.com. Keys are created and regenerated in Workspace
    Settings; regenerating immediately invalidates the previous key. Some execute
    endpoints also accept the key as an auth_token query parameter (webhook flows).
  applies_to: https://api.airops.com/public_api/*
- name: oauth2
  type: oauth2
  scheme: authorizationCode
  description: >-
    OAuth 2.0 authorization-code flow (PKCE S256) used by the hosted MCP server at
    app.airops.com/mcp and OAuth clients. Discovery published at
    app.airops.com/.well-known/openid-configuration and /oauth-authorization-server.
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app.airops.com/oauth/authorize
    tokenUrl: https://app.airops.com/oauth/token
    revocationUrl: https://app.airops.com/oauth/revoke
    introspectionUrl: https://app.airops.com/oauth/introspect
    userinfoUrl: https://app.airops.com/oauth/userinfo
    scopes_supported: [api, openid, profile, email]
    pkce: [S256]
  applies_to: https://app.airops.com/mcp

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/airops-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

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

Get an API key

Free tier, no email required.

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