Skip to main content
PUT
/
v1.0
/
brokermint
/
transaction
Brokermint — Sync Transaction
curl --request PUT \
  --url https://api.lofty.com/v1.0/brokermint/transaction \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: <content-type>' \
  --data '
{
  "id": 10001,
  "agentId": 100001,
  "agentName": "Jane Doe",
  "address": "123 Main St",
  "city": "Los Angeles",
  "state": "CA",
  "zip": "90012",
  "status": "Closed",
  "transactionType": "Purchase",
  "price": 1000000,
  "representing": "Buyer",
  "acceptanceDate": "2023-11-07T05:31:56Z",
  "expirationDate": "2023-11-07T05:31:56Z",
  "closedAt": "2023-11-07T05:31:56Z",
  "closingDate": "2023-11-07T05:31:56Z"
}
'
{
  "code": 0,
  "message": "success"
}

Documentation Index

Fetch the complete documentation index at: https://developer.lofty.com/llms.txt

Use this file to discover all available pages before exploring further.

Headers

​
Authorization
string
required

Bearer [access_token]

​
Content-Type
string
required

application/json

Body

application/json

Brokermint-sourced transaction payload.

​
id
integer<int64>
required

Lofty transaction ID to update. Required; used to look up the existing Lofty transaction and the Brokermint-link record in bm_task_item.

Example:

10001

​
agentId
integer<int64>

Lofty user ID of the agent who will own the transaction. Overwrites the existing ownerId.

Example:

100001

​
agentName
string

Agent's display name. Currently ignored by the handler.

Example:

"Jane Doe"

​
address
string

Street address of the property. Overwrites the stored property address when provided.

Example:

"123 Main St"

​
city
string

City of the property. Overwrites the stored value when provided.

Example:

"Los Angeles"

​
state
string

State or province of the property. Overwrites the stored value when provided.

Example:

"CA"

​
zip
string

Postal / ZIP code of the property. Overwrites the stored value when provided.

Example:

"90012"

​
status
enum<string>

Transaction status from Brokermint. Only the values "Closed" and "Cancelled" trigger a pipeline status change on the Lofty side; any other value is silently ignored.

Available options:
Closed,
Cancelled
Example:

"Closed"

​
transactionType
enum<string>

Transaction type. Case-sensitive. Only the four values below are recognized; any other value is silently ignored.

Available options:
Purchase,
Listing,
Lease,
Other
Example:

"Purchase"

​
price
number

Home price; mapped to Lofty's homePrice field.

Example:

1000000

​
representing
string

Side the agent represented in the deal. Currently ignored by the handler.

Example:

"Buyer"

​
acceptanceDate
string<date-time>

Offer acceptance date. Currently ignored by the handler.

​
expirationDate
string<date-time>

Listing / contract expiration date. Mapped to Lofty's expiration field.

​
closedAt
string<date-time>

Actual close date. Mapped to Lofty's closeTime field.

​
closingDate
string<date-time>

Scheduled closing date. Mapped to Lofty's expectedCloseTime field (note: the Brokermint term "closing date" is interpreted as "expected close" on the Lofty side).

Response

Envelope {code, message}. code=0 indicates applied; code=200060 indicates the transaction was not found (either the Brokermint link is missing or the transaction was deleted). HTTP status is 200 in both cases.

Simple envelope response used by Brokermint webhook and property-address endpoints. Business failures surface as HTTP 200 with a non-zero code; integrators must inspect the code field.

​
code
integer<int32>

Business result code. 0 indicates success; non-zero values indicate a business failure (e.g. 200060 TRANSACTION_NOT_EXIST).

Example:

0

​
message
string

Human-readable message that accompanies the code.

Example:

"success"