Cato Networks · Authentication Profile

Cato Networks Authentication

Authentication

Cato Networks secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyCybersecuritySASESSENetworkingSecuritySD-WANZero TrustGraphQLAPI
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header ()

Source

Authentication Profile

cato-networks-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://api.catonetworks.com/documentation/
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter_name: x-api-key
  description: Cato API key (token) generated in the Cato Management Application (CMA)
    under API management. Every GraphQL request must include the key in the x-api-key
    header along with an accountID argument identifying the target account.
  sources:
  - https://api.catonetworks.com/documentation/
docs: https://api.catonetworks.com/documentation/
account_scope: Requests are bound to a Cato account via an accountID variable; the
  API key is generated per account/admin and can be scoped by admin role and API
  permissions in the CMA.
notes: No OAuth 2.0 / OpenID Connect surface. Authentication is a single API key
  header (x-api-key); there is no scopes artifact because the API does not expose
  OAuth scopes (permissions are governed by CMA admin roles).