Skip to main content
READ · 6 operations · never changes data
Tasks and calendar events — list, fetch by id, “my tasks” across every lead, and available meeting slots. There is no separate mode to pick between to-dos and appointments; both resolve through the same search.
lead_id is an optional filter — omit it for a search across every lead. id fetches one record instead of searching. filters holds whatever extra query parameters the resolved endpoint accepts: lead_id is not used at all for my_tasks/available_slots.
assignee, completed and due_between are not real parameters, despite looking like reasonable filters — no task search variant accepts them. Passing any of them returns a clear error rather than being silently ignored. Fetch by lead_id (or my_tasks) and filter client-side instead.
id accepts either the composite id this tool itself returns (e.g. "12345-task") or a bare numeric id — a bare id is tried against both tasks and appointments before giving up.

​
Showings

kind: "showing" switches the tool to property showings on a lead — the ones partners push through /v2.0/showings and the ones booked inside Lofty. Writes (create/update/complete/delete) live in manage_tasks.