Config API¶
Configuration routes expose developer-defined JSON at two scopes: extension for extension-wide configuration and channel for the current channel context. GET /config returns both scopes together.
All paths below are relative to https://api.muxy.io/v1/e and require the standard Authorization header.
| Method and path | Generated operation reference |
|---|---|
GET /config |
Get all config |
GET /config/channel |
Get channel config |
POST /config/channel |
Post channel config |
PATCH /config/channel |
Patch channel config |
GET /config/extension |
Get extension config |
POST /config/extension |
Post extension config |
PATCH /config/extension |
Patch extension config |
Write bodies¶
The v1 OpenAPI contract declares both POST and PATCH bodies as JSON arrays of RFC 6902 operations. See JSON request bodies for the shared format and use the generated operation page for method-specific details.
Canonical OpenAPI¶
See the raw rest-v1.yaml specification. Sandbox token creation is defined separately in raw sandbox-v1.yaml.