Patch My Party
Changes the user's own role and side (Neutral, Buyer or Seller) on a transaction. Permissions are untouched. Sends the user's current values back in the executed request.
Required variables:
- baseUrl
- apiKey (needs
transactions:write) - userToken
- transactionId, myRole, myRepresenting (set by
Get Transaction Parties)
Authorization
bearerAuth userTokenAuth Partner API key (lyh_...): identifies the calling partner, its scopes and rate limit.
In: header
The user's OAuth 2.1 access token, issued by Land Your Home's OAuth server to this partner's OAuth client. Requests run as this user.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X PATCH "https://example.com/v1/transactions/string/parties/me"{ "data": { "role": "Buyer", "representing": "Buyer" }}Post Transaction Stage
Creates a stage on a transaction the user is an active party on. Only title is required; progress is Not Started (default), In Progress, Blocked or Completed; expectedUpdate/expectedCompletion are ISO 8601 timestamps. dependsOnStageId makes it depend on another stage of the same transaction.
Patch Party
Changes a party's role, representing and/or permissions (per resource: chainNode, propertyDetails, transactionDetails, transactionParty, listingDetails, each { canView, canEdit, canDelete }, merged over the party's current permissions). Omitted fields keep their value. Needs transactionParty.canEdit; you can't grant more than you hold, edit someone who holds more than you, or remove the last party able to edit parties (409 conflict). The executed request re-applies the user's own role.