Features
const url = 'http://localhost:3000/api/v1/features?context=organization';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:3000/api/v1/features?context=organization' \ --header 'Authorization: Bearer <token>'Every feature that can be turned on or off: the core’s own (agents and API keys, share and upload links, portals and sites, BrandHub where the server runs it, usage insights) and the server’s (FEATURES_FILE). At the organization, its rule (on or off in every project, or each project decides) and in how many projects it is on; in the project, whether it is on and what decides it. Admin there.
Any caller; the scope needed is checked on what it acts on.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Where
Responses
Section titled “Responses”Features
object
object
Agents, shares, portals, hub, insights, or one of the server’s own (FEATURES_FILE)
What turning it off does
The core’s own, rather than the server’s
Where it is switched
Where nothing switched it
The organization’s plan has it: false shows the way to one that does instead of a switch
Where its own view is read, under Manage while it is on: a path on this origin when it is the app’s
The organization’s switch: on or off in every project, or each project decides
In the project: whether it is on there; null at the organization
It can be switched here: in a project, only while the organization lets each decide
Example
{ "data": [ { "levels": [ "organization" ], "default": "on", "rule": "on", "from": "organization" } ]}default
Section titled “default”An error
object
object
Examplegenerated
{ "error": { "code": "example", "message": "example", "detail": "example" }}