Create Session with Configs
Update Configs (Full Replacement)
Useupdate_configs to completely replace all configs. Any keys not included will be removed.
Patch Configs (Partial Update)
Usepatch_configs to update only specific keys while preserving others. Pass null/None to delete a key.
PUT vs PATCH Comparison
| Aspect | PUT (update_configs) | PATCH (patch_configs) |
|---|---|---|
| Semantics | Full replacement | Partial update |
| Missing keys | Removed | Preserved |
| Null values | Set to null | Delete the key |
| Return value | None | Updated configs |
Get Configs
Filter Sessions by Configs
Filter sessions by theirconfigs metadata using JSONB containment. Only sessions where configs contains all key-value pairs in your filter will be returned.
Basic Usage
Filter Examples
Multiple Keys
Sessions must match all key-value pairs:Nested Objects
Filter by nested config values:Combine with User Filter
Important Behaviors
- Case-sensitive:
{"Agent": "x"}won’t match{"agent": "x"} - Type-sensitive:
{"count": 1}won’t match{"count": "1"} - Partial matching: filter
{"a": 1}matches configs{"a": 1, "b": 2} - NULL excluded: Sessions with
configs=nullare excluded from filtered results