Mandiant Authentication

generated: '2026-07-20'
method: searched
source: https://docs.mandiant.com/home/mati-threat-intelligence-api-v3
docs: https://docs.mandiant.com
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
  notes: >-
    Mandiant Advantage APIs use an API key (public key) and secret pair issued in
    the Mandiant Advantage console. The key and secret are exchanged for a
    short-lived bearer access token via a token endpoint using an OAuth2
    client-credentials style grant; the returned access_token is then sent on the
    Authorization: Bearer header for subsequent API requests. The Security
    Validation (MSV) API issues its own API key ("Creating a Security Validation
    API Key" in the docs). Derivation was not possible mechanically because
    Mandiant publishes no public OpenAPI specification; this profile is captured
    from the public documentation.
schemes:
- name: mandiant_api_key
  type: apiKey
  in: header
  description: >-
    API key ID and secret issued in the Mandiant Advantage console. Used to
    obtain a bearer access token via the token endpoint.
  sources:
  - https://docs.mandiant.com/home/mati-threat-intelligence-api-v3
- name: bearer_token
  type: oauth2
  flow: clientCredentials
  description: >-
    Access token returned from the token exchange, presented on the
    Authorization: Bearer header. Tokens are short-lived and must be refreshed.
  sources:
  - https://docs.mandiant.com/home/mati-threat-intelligence-api-v3