2026

​

Sales Agent — two endpoints retired

​

Transactions — create custom fields

• POST /v1.0/transaction/customfields — creates a transaction custom field on your team and returns it, id included, so you can populate LeadTransaction.customFields straight away.
• GET /v1.0/transaction/forms?type= — lists the field groups defined for a transaction type.

​

Put the field in a group

{
  "attributeName": "Mailer Sent",
  "attributeType": "date",
  "formIds": [301]
}

​

Two differences from lead custom fields

• anniversary_date and html are not available. Transactions have no recurring-date type, and HTML fields are not exposed through the API. Supported types: text, number, date, percentage, currency, single_select, multi_select.
• Option lists accept both shapes. Transactions store a bare array, leads use an option wrapper. Either is accepted here and normalised, so ["Pending","Closed"] and {"option":["Pending","Closed"]} behave identically.

​

Narrower permissions for custom fields and notes

​

Nothing to do for existing applications

​

Leads — Saved searches: create, update, delete, pause and resume

• POST /v1.0/leads/{leadId}/savedSearches — Create a property alert or market snapshot. Required: category, name (1–255 characters), alertFrequency and criteria. Takes the same values you would pick in the CRM: weekdays and AM / PM for schedule, cadence names (INSTANTLY, DAILY, WEEKLY, BIWEEKLY, MONTHLY, or NEVER to create it paused), and email addresses for recipientEmails, which must belong to the lead. The lead needs at least one email address, and a search with the same filters as an existing one of the lead is refused. sendFirstEmailNow defaults to true for a property alert.
• PUT /v1.0/leads/{leadId}/savedSearches/{savedSearchId} — Update a saved search in place. Only the fields sent change; criteria, when sent, replaces every writable filter at once while filters the API cannot write are kept. category cannot be changed, and searches the lead created on the website cannot be edited (2000011).
• DELETE /v1.0/leads/{leadId}/savedSearches/{savedSearchId} — Delete a saved search and stop its emails for good.
• POST /v1.0/leads/{leadId}/savedSearches/pause — Pause alerts without deleting the searches. Select by categories or by savedSearchIds, not both. Pausing sets the cadence to NEVER, keeps the conditions and schedule, and the search reads back as INACTIVE with the cadence it replaced in frequencyBeforePause. Searches already off are reported as ALREADY_INACTIVE, so repeating the call is safe.
• POST /v1.0/leads/{leadId}/savedSearches/resume — Resume alerts for the given savedSearchIds, each at the cadence it ran at before it was paused. A search whose earlier cadence is unknown stays paused and is reported as PRIOR_FREQUENCY_UNKNOWN; set alertFrequency through the update endpoint instead.

​

Criteria rules

​

Errors

​

Read endpoint changes

​

MCP Server

https://mcp.lofty.com/mcp

​

Leads — Saved searches

• source — comma-separated origins to keep: AGENT_CREATED, LEAD_CREATED, SYSTEM_CREATED. Defaults to all. When migrating to another system, exclude SYSTEM_CREATED — the target usually generates its own, and importing ours duplicates the alerts.
• includeInactive (default false) — include searches whose alerts are switched off. An INSTANTLY cadence counts as active, not off.

​

Fixes

• Tasks V2 / Calendar V2 — startAt / endAt are now parsed correctly when the time zone is supplied separately as timeZoneCode. A bare ISO timestamp such as 2026-03-01T15:00:00 sent alongside a timeZoneCode previously failed to parse and returned HTTP 500 (20005); timestamps carrying their own offset were unaffected. An offset in the string still takes precedence over timeZoneCode.
• Time parameters — a timestamp that can’t be parsed now returns HTTP 400 (20012 INVALID_PARAMETER), with a message naming the offending value and the expected format, instead of HTTP 500 (20005).

​

Agents V2 — Deactivate / Reactivate

• POST /v2.0/agents/{agentId}/deactivate — Releases the agent’s license seat and revokes all sessions and access tokens, while leaving their leads, deals, and data untouched. The caller needs MANAGE_TEAM_AGENT (or MANAGE_TEAM_AGENT_DEPARTMENT); the target can’t be the team owner, an office owner, or the caller.
• POST /v2.0/agents/{agentId}/reactivate — Restores a deactivated agent’s access and re-occupies a seat (fails with SEAT_INSUFFICIENT if none are free).

​

Agents — Multi-license support

• licenses (array of {label, value}) is now returned on GET /v1.0/me, GET /v1.0/users/{userId}, and GET /v1.0/members (both the paginated list and single-account lookup).
• licenseId is now deprecated in favor of licenses.

​

Transactions V2 — Pipeline discovery & type filtering

• Added GET /v2.0/transactions/pipelines — Returns each transaction type’s (Purchase, Listing, Lease, Other) configured stages, so you can look up valid status values instead of hardcoding team-specific stage names.
• GET /v2.0/transactions gains a transactionType query parameter to filter by type, or All to return every type in one call. Defaults to Purchase; an unrecognized value now returns 400 (20012 INVALID_PARAMETER).

​

Leads — remove tags on Update Lead

• tagsRemove (string array) — removes the named tags from the lead. Names are matched literally; a name not currently on the lead is ignored. Applied after tags / tagsAdd.
• clearAllTags (boolean, default false) — set to true to remove all tags from the lead. Takes precedence over tags / tagsAdd / tagsRemove.

​

Communications — Cursor-paged search

​

Webhooks — Ownership-based delivery

• 0 (default) — assignment-based delivery; unchanged behavior.
• 1 — ownership-based delivery; the subscriber also receives callbacks for any lead within their ownership scope (team, office, or personally owned), not only assigned leads.

​

Field Changes

• System Logs (GET /v1.0/systemLogs) — each entry now includes timelineTypeDesc, a human-readable event name paired with the integer timelineType, so you no longer need to map the integer yourself.

​

Fixes

• Leads (GET /v1.0/leads) — the opportunity field is now correctly populated (it previously always returned empty).

​

Communications — single-record lookups

• GET /v2.0/communication/call/{communicationId}
• GET /v2.0/communication/text/{communicationId}
• GET /v2.0/communication/email/{communicationId}

​

Lofty CLI

npm install -g @loftyai/lofty-cli
lofty-cli auth login
lofty-cli leads list --limit 10

​

Transaction V2 Search

​

Lead Query Enhancements

• returnFields: Specify which fields to return (comma-separated), reducing payload size.
• otherFilters: Pass custom LeadFilter overrides for advanced filtering.
• key: Fuzzy search by name, phone, or email in a single parameter.

​

Field Changes

• Calendar V2 — startTime / endTime now accept millisecond timestamps in addition to ISO 8601.
• Manual Log (POST /v1.0/logType) — Added emailSubject, toEmail, fromEmail fields for email log entries.
• Manual Log (POST /v1.0/logType) — The response now returns the created entry’s id.
• Manual Log (GET /v1.0/logType) — Added sort / order parameters to control result ordering, and the response now includes the content field.

​

Sales Agents & AI

• GET /v2.0/sales-agents/by-lead — Get Sales Agent by lead ID
• GET /v2.0/sales-agents/quota — Get current user’s quota
• GET /PUT /v2.0/sales-agent/settings — Query and update settings
• PUT /v2.0/sales-agents/working-lead/{leadId}/mute — Mute a working lead
• POST /v2.0/working-leads/add — Batch add leads to working pool
• POST /v2.0/plan-tasks/create — Batch create plan tasks

​

Intelligent Features (AI)

• POST /v2.0/ai/call-script — Generate call script
• GET /POST /v2.0/ai/call-summary — Get or trigger call summary generation
• POST /v2.0/ai/prepare-insight — Generate prepare insight
• GET /POST /v2.0/ai/lead-analysis — List or create lead analysis tasks

​

Calendar V2

• GET /POST /v2.0/calendar — List and create events
• PUT /DELETE /v2.0/calendar/{calendarId} — Update and delete events
• POST finish/unfinish — Mark events as completed or reopen
• GET /v2.0/calendar/meetings/available — List available meeting slots

​

Tasks V2 Enhancements

• GET /v2.0/tasks/my-tasks — List tasks and appointments assigned to the current user
• POST finish/unfinish — Mark tasks as completed or reopen

​

Lead Activity V2

• GET /v2.0/leads/{leadId}/activities — Unified timeline with calls, texts, and emails in chronological order

​

Notifications

• POST /v2.0/sales-agent/notification/app-push/send-task-reminder — Task reminder push
• POST send-to-agent — Send system SMS or email to agent
• POST /v2.0/sales-agent/ai-number/send-sms-to-agent — Send SMS via AI number

​

Agent Tags

• POST /v1.0/agent/{agentId}/tag/add — Batch add tags with autoCreate support

​

Field Changes

• Listing — Added propertyTypePrimary and propertyTypeSecondary to response
• Note — Added noteId, noteType, idOfType fields
• Calendar V2 — Added taskId field to calendar items

​

Authentication

• Added OAuth 2.0 Client Credentials flow (/oauth/token) for server-to-server integrations
• Added per-app rate limiting and token scope enforcement