Delete a country compliance config
Deletes the workspace’s config for one country. The built-in country defaults
(GET /api/compliance/defaults/{countryCode}) apply again from the next call, message or email.
Deleting a config does not change the workspace retention window, even if this config held the shortest
data_retention_days. Set it explicitly with PUT /api/compliance/retention if needed.
Side effects. Deletes the config row. Writes an audit entry.
Idempotency. Not idempotent in its response: a repeat returns 404 because the config is already gone. The end state is the same.
Access
- Required scope:
full. Signed-in users need theownerrole; admins are refused. - Rate limit: General API — 120 (Starter), 200 (Growth), 300 (Business) or 600 (Enterprise) requests/min per workspace. See Rate limits.
- Plan: Available on every plan. The compliance plan gate on this route does not refuse on any tier today.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Path parameters
ISO 3166-1 alpha-2 code of a supported country, in upper case (CO, MX, BR, US, AR, CL, PE).
Any other value returns 400.