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.
Required variables:
- baseUrl
- apiKey (needs
transactions:write) - userToken
- transactionId, myPartyId, myRole (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
application/json
curl -X PATCH "https://example.com/v1/transactions/string/parties/string"{ "data": { "id": "e74dd2cc-887c-4960-908a-4abd82fca95a", "role": "Buyer", "representing": "Buyer", "permissions": { "chainNode": { "canView": true, "canEdit": true, "canDelete": true }, "transactionParty": { "canView": true, "canEdit": true, "canDelete": true } } }}
