tools
Dry-run a dynamic transfer-destination lookup (no persist)
Changed onResolve a transfer target's destination exactly as the voice host would.
Powers the authoring UI's "what number would this resolve to?" preview: the request's input_mapping is rendered against sample context_vars and executed through the same shared lookup core as a live transfer (same renderer, same revalidation gates, same extraction), so preview and runtime cannot drift. Verifies the revision belongs to the caller's org AND to tool_id (404 otherwise). Persists nothing; API inputs, response bodies, and the resolved destination are never logged.
post/v1/tools/{tool_id}/revisions/{revision_id}/preview-transfer-destination
Request
- The document declares no server URL.
- AuthAPI key in header x-api-key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
tool_idstring uuid required
revision_idstring uuid required
Request body
Response
Successful Response
Changes
- info
endpoint added
- info