Skip to main content
Manage the binding between an API key and a shared Routing Studio preference (one that spans multiple keys or acts as a team default). For the simpler key-first surface that edits rules directly on the key, see /api/v1/keys/{id}/routing-rules. A null preference_id clears the binding; the key then inherits org default → user default → none at request time.

Authentication

Requires a Bearer token with the billing API key scope and access to the key (caller owns it, or has access through the active org).

GET

Read the current binding.

PUT

Set or clear the binding.
string
Preference UUID. Pass null to clear the binding.

Scope rules

  • Personal preferences can only be bound to keys owned by their author.
  • Team preferences can only be bound to keys in the same org.
  • Crossing the boundary returns 400 routing_preference_not_bindable with a vendor-neutral message.

Errors

  • 400 routing_preference_not_bindable — Preference is not visible to the key’s scope.
  • 404 not_found — Key or preference doesn’t exist (or isn’t visible to the caller).