Loading Settler...
Loading Settler...
Loading documentation...
Settler APIs expose deterministic run execution, evidence retrieval, replay, and health posture. Contracts are designed for operator workflows and audit handoff, not dashboard theatre.
Minimum contract expectations before first production call.
• Authenticate with tenant-scoped API keys via X-API-Key.
• Send Idempotency-Key on run creation to prevent duplicate financial actions.
• Expect RFC7807-style problem responses and machine-readable code values.
• Use x-request-id for support escalation and run-level traceability.
/api/v1/runs/api/v1/runs/api/v1/runs/{id}/api/v1/runs/{id}/evidence/api/v1/runs/{id}/replay/api/v1/health | /api/v1/ready | /api/v1/metacurl -X POST "https://your-host/api/v1/runs" \
-H "X-API-Key: set_live_***" \
-H "Idempotency-Key: run-2026-04-close-001" \
-H "Content-Type: application/json" \
-d '{
"name": "April close - Stripe vs Bank",
"sourceAdapter": "stripe",
"targetAdapter": "bank_csv",
"rules": []
}'curl "https://your-host/api/v1/runs/<run_id>/evidence" \ -H "X-API-Key: set_live_***"