Update instance configuration from TOML
PUT
/api/v1/admin/config/toml
const url = 'https://example.com/api/v1/admin/config/toml';const options = { method: 'PUT', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'text/plain'}, body: 'example'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://example.com/api/v1/admin/config/toml \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: text/plain' \ --data exampleUpdates the instance configuration from TOML. It requires a signed-in User with the admin scope and the admin or owner Role. It can return 400 if the request is invalid, 401 if the session is missing or expired and 403 if access is denied. Route: /api/v1/admin/config/toml. Inputs: . A recent account assertion is required. Do not automatically replay this operation after an uncertain result.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”Media typetext/plain
string
Responses
Section titled “Responses”Invalid TOML, a failed validation, or an unreachable sign-in provider. TOML errors carry line and column details; provider errors carry provider.
Media typeapplication/json
The standard API error response: { "error": { ... } }.
object
Example
{ "error": { "code": "bad_request" }}