Retell publishes POST https://api.retellai.com/v3/list-calls — Bearer auth with the same RETELL_API_KEY the v2 get-call path already uses; body takes limit (1-1000), skip, pagination_key, sort_order, and filter_criteria (agent_id, call_type, call_status, start_timestamp_gte/lte); the response carries items[].call_id plus pagination_key/has_more.
https://docs.retellai.com/api-references/list-calls
hotato records Retell as having no confirmed lister (src/hotato/capture.py LIST_STACKS, docs/ADAPTER-STATUS.md), so sweep and the list-driven flows cannot discover Retell calls — every call id has to be supplied by hand. Wiring it means adding retell to LIST_STACKS and implementing the lister against v3 with cursor paging, keeping get-call on v2 (Retell's own versioning), and covering it the way the other listers are covered.
Retell publishes
POST https://api.retellai.com/v3/list-calls— Bearer auth with the sameRETELL_API_KEYthe v2get-callpath already uses; body takeslimit(1-1000),skip,pagination_key,sort_order, andfilter_criteria(agent_id,call_type,call_status,start_timestamp_gte/lte); the response carriesitems[].call_idpluspagination_key/has_more.https://docs.retellai.com/api-references/list-calls
hotato records Retell as having no confirmed lister (
src/hotato/capture.pyLIST_STACKS,docs/ADAPTER-STATUS.md), sosweepand the list-driven flows cannot discover Retell calls — every call id has to be supplied by hand. Wiring it means addingretellto LIST_STACKS and implementing the lister against v3 with cursor paging, keepingget-callon v2 (Retell's own versioning), and covering it the way the other listers are covered.