Memfault · Authentication Profile

Memfault Authentication

Authentication

Memfault secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

AlertsAndroidCrash ReportingDevice ManagementEmbeddedEmbedded LinuxFirmwareIoTLoggingMCUMetricsObservabilityOTAReliability
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

orgAuthToken http
scheme: bearer
basicAuth http
scheme: basic
projectKey apiKey
· in: header (Memfault-Project-Key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/memfault-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: orgAuthToken
  type: http
  scheme: bearer
  bearerFormat: token
  description: |-
    Organization Auth Token. Use "Authorization: Bearer oat_xxx" for automation
    and full API access.
  sources:
  - openapi/memfault-openapi.yml
- name: basicAuth
  type: http
  scheme: basic
  description: Email + password or Email + user API key via HTTP Basic auth.
  sources:
  - openapi/memfault-openapi.yml
- name: projectKey
  type: apiKey
  in: header
  parameter: Memfault-Project-Key
  description: |-
    Memfault Project Key used by devices and ingestion endpoints (chunks,
    latest release lookup, events, coredumps).
  sources:
  - openapi/memfault-openapi.yml