Retrieve a country's default compliance rules
Returns Jelliu’s built-in compliance defaults for a country. They are the same for every workspace, and they
apply whenever the workspace has not saved a config for that country. The response also includes
ai_disclosure_note, which explains why the AI-disclosure default is what it is. It is false for every
country, because no national duty that binds private businesses has been found. Some state and foreign rules
(California, Colorado, the EU) may still apply to you.
Use it as the starting point for PUT /api/compliance/configs.
Consistency. Static data. Responses carry Cache-Control: public, max-age=86400.
Access
- Required scope:
readorwrite. Any signed-in workspace role. - 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.
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.
Response headers
Always public, max-age=86400.
Response
Jelliu’s built-in rules for one country. They apply when the workspace has no saved config for it.