List country compliance configs

View as Markdown
Returns the workspace's saved per-country compliance configs, sorted by `country_code` ascending. The list is not paginated, because there is at most one config per supported country, so at most seven. A country missing from the list uses the built-in defaults from `GET /api/compliance/defaults/{countryCode}`. Reads are open to every role so operators can see the rules they work under. Only the owner can change them, with `PUT /api/compliance/configs` and `DELETE /api/compliance/configs/{countryCode}`. **Access** - **Required scope:** `read` or `write`. 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](/rate-limits). - **Plan:** Available on every plan.

Authentication

AuthorizationBearer
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. | Scope | GET / HEAD | POST / PUT / PATCH / DELETE | Admin-only routes | | --- | --- | --- | --- | | `read` | Yes | No | No | | `write` | Yes | Yes | No | | `full` | Yes | Yes | Yes | 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](/authentication).

Response

Saved configs, sorted by country code.
datalist of objects

Errors

401
Unauthorized Error
403
Forbidden Error
429
Too Many Requests Error