Skip to main content
A transaction in Lofty represents a real estate deal — a purchase, listing, lease, or other arrangement — associated with a specific lead. Transactions track deal financials, pipeline status, close dates, commission, and the property address, and they move through a configurable pipeline as the deal progresses.

​
What is a transaction?

Each transaction belongs to exactly one lead and is managed by an assigned agent. When you create a transaction, you give it a name (typically the property address or deal identifier), a type, and an initial status. From there, you update it as the deal moves through your team’s configured pipeline stages. Transactions support custom fields, letting teams capture deal-specific data beyond the standard schema. You can retrieve your team’s custom field definitions before creating or updating transactions.

​
Key transaction fields

A transaction record’s transactionType is always one of the four concrete types above. When listing transactions with GET /v2.0/transactions, the transactionType query parameter additionally accepts All to return every type in a single call — All is a filter value, never a field value.

​
Transaction lifecycle

Transactions move through a pipeline you configure in Lofty. The typical progression is:
  1. Created — You create the transaction with POST /v1.0/leads/{leadId}/transaction. Supply a transactionName, transactionType, and initial transactionStatus.
  2. In-progress — As the deal advances, you update the status with PUT /v1.0/leads/{leadId}/transaction/{transactionId}. The status value must match one of the statuses configured in your team’s pipeline for the given transactionType.
  3. Closed — Set closeDate and update the status to reflect the closed or cancelled state.
Both transactionType and transactionStatus are case-sensitive and must match your team’s pipeline configuration exactly. Unmatched values silently fall back to the first pipeline or first status — they do not produce an error. Always validate these values against your pipeline configuration before submitting.

​
Creating a transaction

Transactions are created under a specific lead. The transactionName field is required and must not be blank or contain < or > characters.

​
Custom fields

Your team can define custom fields on transactions to capture deal-specific data. Before creating or updating transactions with custom fields, retrieve the field definitions:
This returns the list of custom field definitions for your team, including field names, types, and IDs. Use these definitions to populate custom field values correctly when creating or updating a transaction.

​
Property address

Each transaction can have a property address attached to it separately from the transactionName. This is useful when you need to store a structured address alongside the deal name.

​
Searching transactions (V2)

The V2 transactions endpoint lets you search across transactions without filtering by a specific lead. This is useful for building pipeline dashboards or reports that span multiple leads.
Use GET /v2.0/transactions when building team-level reporting or pipeline views. Use GET /v1.0/leads/{leadId}/transactions when you need all transactions for a specific lead.

​
Endpoint overview