You do not call any special “compliance” endpoint to be covered. Keep using the documented Self-Exclusion and Deposit Limits APIs — the regulatory ingest and reporting run on Anunnaki’s side.
The three obligations
How you get coverage
1
Stream events as documented
Keep calling Self-Exclusion, Deposit Limits, and AML (
POST /v1/aml/event) exactly as described in their reference pages. No extra fields, no extra calls.2
Cross-brand enforcement is automatic
KGC master-list exclusions are matched on every
check regardless of tenant, so a player excluded on one brand is blocked on all of them.3
Reporting happens centrally
Anunnaki compiles and files the threshold (s.28) and self-limitation (s.229A) reports from the data you’ve already sent. Nothing for you to generate or submit.
What this does not change for you
- No new request/response shapes. The compliance coverage is additive and invisible at the API surface.
- No tipping-off risk. As with AML, never surface compliance internals (rule codes, report status, master-list membership) to end users — use neutral language only.
- Report generation is internal. The admin ingest and report-export tooling is operated by Anunnaki and is intentionally not part of this public reference.
Questions about your brand’s KGC coverage? Contact Anunnaki compliance via your integration manager.