GEgetaxonflow
OJK Compliance

Get OJK retention status

Reports 5-year (1825-day) retention compliance for OJK audit data. compliance_status is non_compliant when the configured retention is below the 1825-day minimum.

Enterprise Feature.

get/api/v1/ojk/audit/retention

Request

Query parameters

data_typesstring

Comma-separated list of data types to report on. Narrows the report; omit it for every data type. Each entry is derived from its backing store (count, oldest and newest record, and a status of compliant / short_history / no_data / unknown); a store that cannot be read reports unknown, never no_data (#3242).

Headers

X-Tenant-IDstring

Deprecated fallback. Every OJK route is scoped to the caller's ORGANIZATION via X-Org-ID (#3242); X-Tenant-ID is used only when X-Org-ID is absent, which covers single-identifier deployments where the two values are the same. When both are present the organization wins. A request carrying neither header, or a whitespace-only value, is rejected with 400 (code missing_org).

X-Org-IDstring

Organization identifier — the authoritative OJK scope. Set by the AxonFlow agent from the validated client credential on every proxied route, so a caller cannot choose it.

Response

Retention status

compliance_status'compliant' | 'non_compliant'
frameworkstring
retention_daysinteger
min_retention_daysinteger
next_cleanupstring date-time

Never set by the current implementation (omitted)

Example response

{
  "framework": "OJK_BI_COMBINED",
  "min_retention_days": 1825
}

Changes

No recorded changes to this operation across all 1 revision of this API.