API Documentation

The complete reference for the Mulisa REST API. Pick an endpoint or guide from the sidebar — the documentation panel updates in place and every selection is deep-linkable.

Overview

Mulisa is API-first. Every capability in this console — screening, rules, sandbox runs, blacklists, webhooks, and reporting — is available over the same versioned REST API your systems integrate with. Select an endpoint from the sidebar to see its full documentation.

Authentication

Authenticate API requests with a bearer key. Use your live key (jc_live_...) for production screening and your sandbox key (jc_test_..., issued at onboarding) for testing. Console pages authenticate via your session instead.

Authorization: Bearer jc_live_...
# or
X-Api-Key: jc_live_...

Base URLs

https://api.aml.jengacore.com/v1   # dedicated API host (recommended)
https://aml.jengacore.com/api/v1   # primary host

Webhook signatures

Webhook payloads are signed with HMAC-SHA256 using the secret returned when the webhook was created. Verify the X-Jengacore-Signature header (t=<unix>,v1=<hex>) against timestamp.raw_body before trusting an event. See Webhooks & event catalog for receiver examples.