Skip to main content
The MKA1 API exports your organization’s audit records over HTTP, so you can pull them on a schedule into your own SIEM, log store, or monitoring. These are the same records the console’s Audit page shows and exports. For endpoint details, see the API Reference and open the Audit group.

Requirements

Every export covers only the organization the API key belongs to. You can’t export another organization’s records. Requests made on behalf of an end user, with an exchanged token or X-On-Behalf-Of, can’t export.

What you can export

The three list exports take these query parameters:
  • format: json (the default) returns a JSON array of rows. csv returns a header row and one line per row.
  • dateFrom and dateTo: ISO 8601 timestamps that bound the records returned.
  • order (cases and gateway requests): newest (the default) or oldest. Gateway requests also accept slowest. Misuse findings are always newest first.
Each export is recorded in your organization’s audit trail.

Pull a time window

To load records into a SIEM, export one fixed window per run, for example the previous hour, and load the file.

Row limit

A list export returns up to 100,000 rows. Three response headers tell you whether the file is complete: If x-export-truncated is true, split the window into smaller dateFrom/dateTo ranges and export each one.