Follow the contract API lifecycle

​

Lifecycle

​

Follow the lifecycle

1. Create a contract from an approved template with Legal/CreateContract. Assign each approved Legal Identity to its exact role.
2. Have the initiating party retrieve and review the returned contract, then sign its assigned role.
3. Send a contractProposal stanza to the counterparty’s bare or full JID. A sent: true response confirms sending, not receipt or acceptance.
4. Confirm the counterparty received the matching contractId and role, then retrieve the contract with Legal/GetContract.
5. Show the counterparty the exact returned human-readable contract. Treat explicit user confirmation as the acceptance boundary.
6. Sign the counterparty’s role with Legal/SignContract.
7. Retrieve the contract again and verify the state required by the template. Confirm every required role signature instead of treating a successful HTTP response as completion.

​

Construct a contract signature

s1 = username:HTTP-Host:localName:namespace:keyId
keySignature = Base64(HMAC-SHA256(key=UTF8(keyPassword), data=UTF8(s1)))
s2 = s1:keySignature:nonce:legalId:contractId:role
requestSignature = Base64(HMAC-SHA256(key=UTF8(accountPassword), data=UTF8(s2)))

​

Related endpoints

• Propose a contract template
• Create a contract
• Send a proposal over XMPP
• Sign a contract
• Get contract