Post Chain
Creates a chain with the user's transaction(s). selling makes the user the Seller of that property, buying makes them the Buyer (selling + buying links the purchase to the sale); or send thirdParty ({ role, representing, property }) on its own to join as, for example, an agent.
A property is { address: { addressLine1, country, ... }, saleState, currency, askingPrice?, acceptedPrice?, agent?, url?, image? }.
Required variables:
- baseUrl
- apiKey (needs
chains:write) - userToken
Sets newChainId and newTransactionId for the requests that follow.
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
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/v1/chains"{ "data": { "chainId": "1b18a121-73df-4412-88b8-b71545b6c9fe", "sellingTransactionId": "a4b26e43-9cba-4715-a8a4-a22ae0c3ecd4", "buyingTransactionId": "973d31a5-f2ad-4032-b00c-24e2a4bb4a91", "thirdPartyTransactionId": null }}Get Chains
Happy path: the chains the user is in, with their links and a summary of each transaction.
Post Chain Link
Links two existing transactions inside this chain: transactionId depends on dependencyId. Needs chainNode.canEdit on both, at least one must already be in the chain, and neither may be in another chain (merge those instead). Linking the same pair again returns the existing link (201 with the same linkId). The executed request uses transactions the user has no permission on, so it returns 403 forbidden; the success states are examples.