mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
b931df3a5f
For some signing implementations, such as ed25519, a non-default hash implementation must be specified when creating the Gateway connection in client applications. Rather than relying on the default hash algorithm, it is probably good practice in general to specify an algorithm that is compatible with your signing implementation. This change explicitly specifies the hash algorithm to raise visibility of the option to select the hash algorithm. Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com> |
||
|---|---|---|
| .. | ||
| web | ||
| .gitignore | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| README.md | ||
Asset Transfer REST API Sample
This is a simple REST server written in golang with endpoints for chaincode invoke and query.
Usage
-
Setup fabric test network and deploy the asset transfer chaincode by following this instructions.
-
cd into rest-api-go directory
-
Download required dependencies using
go mod download -
Run
go run main.goto run the REST server
Sending Requests
Invoke endpoint accepts POST requests with chaincode function and arguments. Query endpoint accepts get requests with chaincode function and arguments.
Sample chaincode invoke for the "createAsset" function. Response will contain transaction ID for a successful invoke.
curl --request POST \
--url http://localhost:3000/invoke \
--header 'content-type: application/x-www-form-urlencoded' \
--data = \
--data channelid=mychannel \
--data chaincodeid=basic \
--data function=createAsset \
--data args=Asset123 \
--data args=yellow \
--data args=54 \
--data args=Tom \
--data args=13005
Sample chaincode query for getting asset details.
curl --request GET \
--url 'http://localhost:3000/query?channelid=mychannel&chaincodeid=basic&function=ReadAsset&args=Asset123'