Config
Read and replace per-section app configuration.
Config endpoints read and replace one configuration section at a time. Each section is a self-contained object; there is no endpoint that reads or writes the whole config in one call.
Endpoints
| Method + path | Scope | Notes |
|---|---|---|
GET /v1/config/:section | Read | Read one configuration section. Returns {section, config:<obj>}. |
PUT /v1/config/:section | Write | Replace one configuration section. Full-object replace: send the whole section object, not a partial patch. Returns {section,config}. An unknown section returns 422. |
PUT replaces the whole section
PUT /v1/config/:section replaces the entire section object, it is not a partial patch. Read the section first with GET, merge your change into the full object client-side, then PUT the merged result - omitted fields are dropped, not left as-is.
Config sections
These are the only valid values for :section:
| Section |
|---|
vad |
diarization |
speaker-identification |
meeting-detection |
global-shortcut |
audio-player |
custom-words |
initial-prompt |
Client exposure
The CLI uses meetily-pro config get and meetily-pro config set; the write flag is --json-body, not --json. The Python SDK exposes config.get() and config.set(). There is no MCP tool for setting config: config writes are available over HTTP, CLI, and the SDK only.
Read a config section
curl -s http://127.0.0.1:8420/v1/config/vad -H "Authorization: Bearer $MEETILY_PRO_TOKEN"meetily-pro config get vadfrom meetily_agent import MeetilyClient
print(MeetilyClient().config.get("vad"))Replace a config section
curl -s -X PUT http://127.0.0.1:8420/v1/config/vad -H "Authorization: Bearer $MEETILY_PRO_TOKEN" -H "content-type: application/json" -d '{"enabled":true,"sensitivity":0.6}'meetily-pro config set vad --json-body '{"enabled":true,"sensitivity":0.6}'from meetily_agent import MeetilyClient
print(MeetilyClient().config.set("vad", {"enabled": True, "sensitivity": 0.6}))Last updated on