Model MatchHelp

Properties

Flag a transaction on a property's history

postapi.modelmatch.com/v1/properties/{mmPropertyId}/transaction-flags

Report that a listing, sale or mortgage on a property's history looks wrong — a wrong loan amount, loan officer or company, a duplicate, missing details, or a missing transaction. The flag is reviewed by the Model Match data team; this call only records it and answers immediately. Flagging the same transaction for the same reason again while the first flag is still open returns the first flag's id.

Authorization

x-api-keystringrequired

API key or OAuth token. See Authentication.

Path parameters

mmPropertyIdstringrequired

The property's mmPropertyId.

Body application/json

addressstringrequired

The property's address as the user saw it.

detailsstring

What is wrong, in the user's words (up to 2000 characters). Markup and control characters are removed.

eventDatestringrequired

The row's date as shown (ISO date preferred).

eventIdstringrequired

The listing / sale / loan id of the history row being flagged.

eventSummarystringrequired

The row's one-line summary as shown.

eventTypeenumrequired
Options:listingsoldmortgage
profileobject

The profile the user flagged it from, when there was one.

Show child attributes
idstringrequired
typeenumrequired
Options:agentloan-officercompany
urlstring

Link to the profile in the app. Ignored unless it is a public http(s) URL.

reasonenumrequired
Options:wrong-loan-amountwrong-lo-or-companywrong-property-detailsduplicatemissing-detailsmissing-transactionother

Responses

202objectRecorded. Review happens afterwards.
Show attributes
dataobjectrequired
Show child attributes
idstringrequired

The flag id.

400objectValidation error
401objectUnauthorized
403objectForbidden (authenticated, but missing required context — e.g. no active organization)
404objectNot found
413objectThe request body is too large.
415objectThe body must be sent as `application/json`.
429objectToo many flags in the last 24 hours. Try again later.
503objectSearch timed out or the cluster is overloaded — retry after `Retry-After` seconds.