Forum Discussion

Copper Contributor

Jul 04, 2018

ABW - Obtaining the Contract Id (or LedgerIdentifier) on a newly created contract via Rest API?

Although I understand that a new contract will be written asynchronously (although a contract record is immediately written to Sql Server with a pending ledger identifier once it is pulled off the qu...

blockchain

Zeyad Rajabi

Microsoft

Calling POST /api/v1/contracts should return back the ID of the contract, which you can use to query with GET.

Stuart Corrans

Copper Contributor

Jul 10, 2018

You're right, thanks, it's the GatewayApi sample code which is discarding the contractid:

https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/rest-api-samples/dotnet/GatewayApi.cs#L460

Replacing string.Empty with await msg.Content.ReadAsStringAsync() returns the newly allocated contract id as a raw string

Stuart Corrans
Copper Contributor
Dec 04, 2018
For anyone interested, ABW 1.5 and hopefully onward now DO allow for asynchronous tie-ups of the Request and Response on the Messaging API : https://docs.microsoft.com/en-us/azure/blockchain/workbench/messages-overview

The user-supplied `requestId` that Contract and Contract Action requests accept is then echoed back on the ABW EventGrid (and I think also on the egress Service Bus topic), along with the assigned ContractId ContractAddress (Contract Creates) and ContractActionId / TransactionId (Contract Actions)

Forum Discussion

ABW - Obtaining the Contract Id (or LedgerIdentifier) on a newly created contract via Rest API?

Share

Resources