Skip to content

Configuration โ€‹

System configuration โ€” the key/value store that controls tenant-wide platform settings (mail server, token lifetimes, feature flags, integration secrets, etc.). Config keys are read and modified individually; the catalogue of available keys is returned by the list endpoint.

Scopes โ€‹

ScopeReach
adminAll configuration endpoints, including the mail-config verifier.

Endpoints โ€‹

Get All Config Keys โ€‹

GET /api/admin/config/

Returns every configuration key the platform recognizes, along with its current value (or whether the value is sensitive/masked).

Required scope: admin ยท also accepts API key

Response 200 โ€” list of config-key records.

Get Config by Key โ€‹

GET /api/admin/config/{key}

Returns the value (or masked representation) of a single configuration key.

Required scope: admin ยท also accepts API key

Path parameters

NameTypeRequiredDescription
keystringyesConfiguration key name.

Response 200 โ€” config-key record.

Replace Config โ€‹

PUT /api/admin/config/{key}

Replaces the value of a configuration key.

Required scope: admin

Path parameters

NameTypeRequiredDescription
keystringyesConfiguration key name.

Request body โ€” the new value, shape depends on the key being set (see GET /api/admin/config/ for the expected type per key).

Response 200 โ€” the updated config record.

Update Config Partially โ€‹

PATCH /api/admin/config/{key}

Partial update of a configuration key. Useful for object-typed keys where you only want to change one nested field.

Required scope: admin

Path parameters

NameTypeRequiredDescription
keystringyesConfiguration key name.

Request body โ€” the patch to apply.

Response 200 โ€” the updated config record.

Verify Mail Config โ€‹

GET /api/admin/config/mail/verify

Sends a test email using the current mail configuration to verify it works end-to-end. An optional token query parameter is accepted for tokenized verification flows.

Required scope: admin

Query parameters

NameTypeDescription
tokenstring | nullOptional tokenized verification.

Response 200 โ€” confirmation payload (or 4xx if the mail config is broken).

See also โ€‹

  • System Defaults โ€” force-recreate default objects (often used after a config-driven schema change).
  • System Health โ€” runtime health checks that complement static config inspection.

S-Launch