Post Chain Merge
The user must be an active party on sharedTransactionId. Anything else is 403 forbidden.
Required variables:
- baseUrl
- apiKey
- userToken
- chainId
Path Parameters
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/v1/chains/string/merge"{ "data": { "chainId": "1b18a121-73df-4412-88b8-b71545b6c9fe", "mergedChainId": "3876d6a9-bc6e-4225-b459-b4c480f982fd" }}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.
Post Chain Transaction
Adds a transaction for a property to this chain, next to transactionId, which needs chainNode.canEdit. relation: "dependency" makes transactionId depend on the new transaction; "requirement" makes the new transaction depend on transactionId. An existing transaction on the property is reused unless useExistingTransaction is false. If that property is already in this chain, or in another chain, nothing is written and the response is 409 conflict (the other chain's ids are included in error.details only if the user is a party there).