Create a tool revision

Configuration for an API_CALL tool, stored in Tool.configuration.

Supports {{variable}} placeholders in url, headers, and body that are resolved at execution time from the tool's input variables and runtime metadata (via {{metadata.key}}).

Operator-supplied config for a call_transfer target (ENG, voice).

A transfer target carries either a static destination (E.164 or sip: URI) or a dynamic destination_source (api_tool reference that resolves the destination at transfer time). The two are mutually exclusive. mode is always "cold".

destination validity (E.164 or sip: URI) is enforced at the service layer via :func:~src.custom_tools.api._shared.transfer_target.validate_transfer_target_config so a bad destination surfaces as a clean 422. The label / when-to-use are carried on the Tool's name / description, not here.

The projection applied to a tool response.

Configuration for an API_CALL tool, stored in Tool.configuration.

Supports {{variable}} placeholders in url, headers, and body that are resolved at execution time from the tool's input variables and runtime metadata (via {{metadata.key}}).

A call_transfer revision's stored target, surfaced on reads.

ToolRevisionResponse.configuration is api_call-typed and parses to None for a transfer config (it has no url), so this field carries the destination/mode back for the transfer-target picker. label / when_to_use come from the parent Tool's name / description.

Either destination (static) or destination_source (api_tool dynamic) is present, never both. The unused variant is omitted from serialization.

The projection applied to a tool response.

Impact report shared by preflight analysis and successful promotion.

Pre-prod: findings are advisory warnings — promotion always succeeds. The has_blocking / active_blocking_* fields retain their literal blocking semantics (and therefore remain false/zero today).