Get Config
const url = 'https://example.com/config';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/configResponses
Section titled “Responses”Successful Response
object
Read-only posture block (issue #123). Field-level Fernet encryption is mandatory (startup fails closed without a working key), so this mostly attests rather than warns. Since #137 the narrative layer (payee names, descriptions, memos, schedule names, audit/event payloads) is encrypted too; only the numeric skeleton (amounts, dates, statuses, ltree paths, ids) and the readmodel v2 views over it stay plaintext by design (decision 36). Storage-level encryption remains a deployment concern the app can’t attest.
object
User-facing SimpleFIN sync schedule (UTC).
Presets rather than raw cron. hour/minute apply to daily only;
the interval presets are anchored so every choice lands a fresh sync just
before the 06:45 UTC matching job, and hourly (24 runs/day) sits
exactly at the SimpleFIN Bridge budget — the per-connection fetch guard
fails soft beyond it.
Example
{ "values": { "sync_schedule": { "preset": "daily" } }}