Skip to main content
READ · 16 operations · never changes data
Everything the team and organization are configured with. The kind values mirror the five sections of the Lofty back office, so a kind name tells you which screen it corresponds to.
Each kind only needs the parameter(s) listed below — the rest of account?/pond_id?/routing_type?/filters? don’t apply and are ignored: routing_type accepts only "agent_lead", "lender_lead" or "assistant_lead" — no other value.
filters.currPage is 0-based — currPage: 1 is the second page, not the first.
Looking a member up by their raw numeric user id is deprecated upstream and isn’t exposed under any kind — use members.find (by account email) instead.
A lead’s own system event log (stage changes, assignment/routing, subscriptions, smart-plan tasks) is search_lead_activities with channel: "system_log", not this tool — it’s per-lead data, not team/organization configuration.