Meow · Authentication Profile

Meow Authentication

Authentication

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

CompanyBankingFintechBusiness BankingPaymentsCardsInvoicingTreasuryCryptocurrencyWebhooksMCPAPI
Methods: apiKey, oauth2 Schemes: 3 OAuth flows: authorizationCode API key in: header

Security Schemes

apiKeyAuth apiKey
· in: header (x-api-key)
entityScope apiKey
· in: header (x-entity-id)
mcpOAuth oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/meow-openapi.yaml
docs: https://developer.meow.com/authentication
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
notes: >-
  The REST API authenticates with an API key in the x-api-key header. Keys are
  created and scoped from the Meow dashboard and carry granular scopes (see
  scopes/meow-scopes.yml). For API keys with access to multiple entities, the
  optional x-entity-id header scopes a request to a specific entity; list
  accessible entities with GET /api-keys/accessible-entities. The Meow MCP
  server adds a second, OAuth 2.1-with-PKCE surface for AI assistants at
  https://mcp.meow.com (plus an API-key/bearer CLI surface at
  https://mcp.meow.com/cli); it acts as an authorization proxy in front of
  Meow's identity provider with a post-login scope picker over meow.* scopes.
schemes:
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter: x-api-key
  description: Your Meow API key, sent in the `x-api-key` header for authentication.
  sources:
  - openapi/meow-openapi.yaml
  docs: https://developer.meow.com/authentication
- name: entityScope
  type: apiKey
  in: header
  parameter: x-entity-id
  description: >-
    Optional header to scope a multi-entity API key to a specific business
    entity (UUID). Not a standalone credential; used alongside x-api-key.
  sources:
  - openapi/meow-openapi.yaml
- name: mcpOAuth
  type: oauth2
  flow: authorizationCode
  pkce: true
  server: https://mcp.meow.com
  description: >-
    OAuth 2.1 with PKCE for the Meow MCP server. meow.read is always granted;
    meow.transfers, meow.cards, and meow.billing are opt-in via a post-login
    scope picker gated by the user's role.
  scopes:
  - meow.read
  - meow.transfers
  - meow.cards
  - meow.billing
  sources:
  - https://developer.meow.com/mcp/authentication