Skip to main content
Fetch, modify, or hard-delete a single Routing Studio preference. Visibility: author or any member of the owning org. Non-members receive 404 so the existence of team preferences is never leaked.

​
Authentication

Requires a Bearer token with the billing API key scope.

​
GET

Fetch the full preference snapshot.

​
PATCH

Update fields on an existing preference. Sending rules or examples replaces the entire collection — both are treated as single documents on save. At least one field is required.
​
string
Preference name (1–128 chars).
​
string
Free-text description (≤512 chars).
​
object[]
Replacement rule set (≤50 rules).
​
object[]
Replacement few-shot examples (≤30).
​
object
Replacement per-mode confidence floors.
​
boolean
Pause/unpause without deleting.
​
boolean
Promote/demote default. One default per scope.
Team-scoped preferences require the manageWebhooks permission on the active organization.

​
DELETE

Hard delete. Cascade-removes every key binding pointing at this preference — previously-bound keys revert to the resolution cascade (org default → user default → none).

​
Errors

  • 400 routing_preference_invalid — Validation failure on PATCH.
  • 404 not_found — Preference doesn’t exist or isn’t visible to the caller.
  • 409 conflict — Default-uniqueness violation.