GEgetaxonflow
OJK Compliance

Check OJK compliance readiness

Validates readiness for an OJK regulatory audit across five checks: Data Retention, PII Detection, Human Oversight, Audit Logging, and Breach Notification.

Every check QUERIES the state it names or reports unknown (#3242) — four of the five were previously unconditional pass literals. Check statuses are pass, warning, fail or unknown, and each carries details describing what was OBSERVED plus an observed measurement.

Scoring: a pass counts 1, a warning 0.5, a failure 0, and an unknown check scores ZERO while STILL counting in the denominator — an unobservable dimension must drag the score down, never inflate it. measured_checks / unknown_checks expose the split. ready requires no failures, no unknowns, and a score of at least 80.

Enterprise Feature.

get/api/v1/ojk/audit/readiness

Request

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

Compliance readiness assessment

readyboolean

True at score 80+

scoreinteger
frameworkstring
recommendationsstring[]

Example response

{
  "framework": "OJK_BI_COMBINED"
}

Changes

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