POST/trusted-schemas-registry/v3/jsonrpc
The JSON-RPC API provides methods assisting the construction of blockchain transactions and interaction with the ledger.
Request
- application/json
Bodyrequired
The body follows the JSON-RPC 2.0 specification.
It requires the following fields:
- jsonrpc: must be exactly "2.0"
- method: method to be invoked
- params: method parameters
- id: identifier established by the client
API Methods
insertSchema
Call to build an unsigned transaction to insert a new schema. This method requires an access token with "tsr_write" scope and having the required attributes assigned in Trusted Policies Registry.
Parameters:
- from: Ethereum address of the signer
- schemaId: schema ID converted into hex string
- schema: Content. This field must be a JSON stringified and converted into hex string
- metadata: Metadata of the first version. This field must be a JSON stringified and converted into hex string
updateSchema
Call to build an unsigned transaction to update an schema. This method requires an access token with "tsr_write" scope and having the required attributes assigned in Trusted Policies Registry.
Parameters:
- from: Ethereum address of the signer
- schemaId: Schema ID
- schema: Content. This field must be a JSON stringified and converted into hex string
- metadata: Metadata. This field must be a JSON stringified and converted into hex string
updateMetadata
Call to build an unsigned transaction to update the metadata of a schema revision. This method requires an access token with "tsr_write" scope and having the required attributes assigned in Trusted Policies Registry.
Parameters:
- from: Ethereum address of the signer
- schemaRevisionId: Schema revision ID
- metadata: Metadata. This field must be a JSON stringified and converted into hex string
sendSignedTransaction
Call to send a signed transaction to the blockchain.
Must be exactly "2.0"
Method that needs to be invoked
Array of parameters
Identifier established by the client
Responses
- 200
- 400
Response
- application/json
- Schema
- Build tx
- Send Transaction
Schema
- MOD2
Must be exactly "2.0"
Same identifier established by the client in the call
result object
Result of the call
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"from": "0x416e6e6162656c2e4c65652e452d412d506f652e",
"to": "0xFde86148db58f57787C06BeAf63a9c3f789357b3",
"data": "0x0000...",
"nonce": "0x00",
"chainId": "0x1b3b",
"gasLimit": "0x10000",
"gasPrice": "0x00",
"value": "0x00"
}
}
{
"jsonrpc": "2.0",
"id": 1,
"result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}
Bad request
- application/problem+json
- Schema
- Bad Request
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"title": "Bad Request",
"status": 400,
"detail": "Bad request"
}