GEgetaxonflow
OJK Compliance

Acknowledge a breach notification

Marks a submitted breach notification as acknowledged by the authority. Only the submitted -> acknowledged transition is valid; acknowledging a draft/overdue/failed/already-acknowledged record returns 409.

Enterprise Feature.

post/api/v1/ojk/breach/acknowledge

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.

Request body

idstring required

Breach notification id

Response

Breach notification acknowledged (returns the updated record)

idstring

Server-assigned

incident_timestampstring date-time required
discovery_timestring date-time required
notification_deadlinestring date-time

Server-computed (discovery_time + 72h)

data_subjects_affectedinteger required
data_types_involvedstring[] required
descriptionstring required
remediation_stepsstring[] required
notified_authoritystring

Defaults to MOCDA

status'draft' | 'submitted' | 'acknowledged' | 'overdue' | 'failed'
submitted_atstring date-time
acknowledged_atstring date-time
created_atstring date-time

Changes

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