Sign in

v1

latestOpenAPI 3.0.12026-07-22120163333.7 KB
Lead Transaction

Brokermint — Sync Transaction

Callback endpoint for Brokermint integration to sync transaction updates into Lofty.

The transaction must be linked to Brokermint via the Lofty UI before this endpoint can update it. See the request body schema for supported fields.

put/v1.0/brokermint/transaction

Headers

Authorizationstring required

Bearer [access_token]

Content-Typestring required

application/json

Request body

idinteger required

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

agentIdinteger

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

agentNamestring

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

addressstring

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

citystring

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

statestring

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

zipstring

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

status'Closed' | 'Cancelled'

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.

transactionType'Purchase' | 'Listing' | 'Lease' | 'Other'

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

pricenumber

Home price; mapped to Lofty's homePrice field.

representingstring

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

acceptanceDatestring date-time

Offer acceptance date. Currently ignored by the handler.

expirationDatestring date-time

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

closedAtstring date-time

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

closingDatestring 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).

Example request

{
  "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"
}

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.

codeinteger

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

messagestring

Human-readable message that accompanies the code.

Example response

{
  "message": "success"
}