Skip to main content
PUT
Write organization configuration

Authorizations

Authorization
string
header
required

OAuth 2.0 client credentials flow. Contact timeback@trilogy.com to request credentials for your application.

Path Parameters

sourcedId
string
required

Unique identifier of the organization

Body

application/json

Map of config keys to values to upsert or delete (null to delete)

config
object
required

A flat map of config key → value. null deletes the row (reverts to inherited / default). Keys not present are untouched. Registered keys (above) use their declared types and are Zod-validated. Unregistered partner-defined keys are stored as plain text and must be string or null. Keys must be safe identifiers (1–255 chars, ^[A-Za-z_][A-Za-z0-9_-]*$); reserved JS prototype slots are rejected. Top-level arrays are rejected.

Response

Configuration updated successfully