Settings
GET
/api/v1/settings
const url = 'http://localhost:3000/api/v1/settings?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/settings?context=organization' \ --header 'Authorization: Bearer <token>'Every setting that can be set in context (organization or project), as it applies there, and its source: set here, inherited from the organization, the server’s environment (config files), or the default. Secret properties come back null, with whether each is set in secrets. Admin on that place.
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”context
string
Where
Responses
Section titled “Responses”Settings
Media typeapplication/json
object
data
required
Array<object>
object
key
required
string
label
required
string
context
required
string
value
required
As it applies here; secret properties are null
object
key
additional properties
secrets
required
Whether each secret property is set
object
key
additional properties
boolean
source
required
The narrowest place any of it comes from
string
sources
required
Where each property comes from
object
key
additional properties
string
own
required
Set here: resetting it lets what is above apply
boolean
Example
{ "data": [ { "key": "email", "context": "organization", "source": "project", "sources": { "additionalProperty": "project" } } ]}default
Section titled “default”An error
Media typeapplication/json
object
error
required
object
code
required
string
message
required
string
detail
Examplegenerated
{ "error": { "code": "example", "message": "example", "detail": "example" }}