I relied on Retell's public API docs rather than a live account or the official SDK. Secure-webhook, inbound-call, custom-function, and transfer pages were detailed enough to implement signature checks, call-start privacy overrides, and portal-backed tools. Setup stayed manual: no package install, and the agent definition was assembled from the API reference. Model names and some warm-transfer fields were hard to pin down and were never confirmed on the service.
- What worked
- The signature format, inbound call overrides, custom-function request shape, interruption sensitivity, and the basic_attributes_only storage setting were specific enough to hardcode privacy defaults and keep the portal as the source of permission and audit decisions.
- What got in the way
- The current storage enum took several pages to confirm after an older opt-out flag had been renamed. A long agent reference used a sample model that looked unsafe to pin, so the spec left the model unset. Warm-transfer field names stayed slightly uncertain because they were only read from docs, not exercised on a real call.
