Store config for a namespaced key

Fully replaces the value stored at the key — this is not a patch, so send
the complete object every time. Responds with the stored value.

Write ?brand=_base to set the base for a namespace, or use
/channel_api/v1/connection_config/base for the connection-wide base.

Pass ?validate=true to check the value against the config schema
registered for your connection before it is stored — see the parameter
description below.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

Example namespace. Any single namespace parameter is accepted.

boolean

Off by default. When true, the value is checked against the config
schema your connection is registered against and nothing is stored
unless it passes.

Validation runs against the value the write would resolve to —
the stored bases with this payload merged over them — so a required
field supplied once in brand:_base satisfies every key beneath it.
Keys the schema doesn't describe are stored as normal.

Responds 422 when your connection has no schema for the namespace,
or with details listing every field that failed. Not available on
base configs (?brand=_base or /base), which are schema-exempt:
those respond 400.

Note that validate is reserved, so it can't also be used as a
namespace name.

Body Params
config_value
object
required

The config object to store. Free-form, but must be an object.

Headers
string
required

Bearer

Responses
200

stored

400

more than one namespace parameter, or validate on a base config

422

config_value missing or not an object, or it fails schema validation

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here!