Flags
GET
/api/flags
const url = 'http://localhost:8000/api/flags';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:8000/api/flags \ --header 'Authorization: Bearer <token>'Return the runtime feature flags the UI branches on.
pg_lead_store reports the effective availability (use_pg_store())
rather than the raw config bool, because that is what actually gates the
Postgres-only surfaces (intent watches, on_signal triggers). It degrades
to the raw config flag if the store module can’t be imported.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Responses
Section titled “Responses”Successful Response
Media typeapplication/json
Flags
object
allow_legacy_outreach
required
Allow Legacy Outreach
boolean
automations_enabled
required
Automations Enabled
boolean
intent_poller_enabled
required
Intent Poller Enabled
boolean
pg_lead_store
required
Pg Lead Store
boolean
Examplegenerated
{ "allow_legacy_outreach": true, "automations_enabled": true, "intent_poller_enabled": true, "pg_lead_store": true}Validation Error
Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationErrorobject
ctx
Context
object
input
Input
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
Examplegenerated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}