The Tessera API consists of the following parts:
quorum-to-tessera- The privacy-enabled Ethereum client uses the
quorum-to-tesseraAPI to check if the associated Tessera node is running, and to send and receive private transactions.
peer-to-peer- Tessera uses the
peer-to-peerAPI to perform discovery, and to send and receive encrypted payloads.
third-party- Tessera uses the
third-partyAPI to store encrypted payloads for external applications, for example,
Configure the API servers in the Tessera configuration file.
Define API versions
Every client side request (such as
/partyinfo) includes a header parameter called
tesseraSupportedApiVersions that lists the supported API versions.
Exchanging and storing the supported API versions enables Tessera nodes to know which API versions are supported by peers.