Daml ledger allocate-parties

I am using the Postgres Driver for daml.

We add new parties dynamically, as a part of an onboarding process.

Which is the best way to allocate these new parties?
Is it safe to run the daml ledger allocate-parties each time? Is there SDK support for it?


1 Like

It is safe, but depending on your situation, you may want to rather use the Ledger API RPC PartyManagementService#AllocateParty (which is what daml ledger allocate-parties uses), which can allow you to integrate party allocation in an existing application.

EDIT: as brought up by @Gary_Verhaegen in the following answer the JSON API also allows you to allocate a party. That is likely to be easier than and preferable to interacting with the Ledger API directly.


If you have a JSON API running, I’d say curl is probably the most lightweight solution.

curl -XPOST \
     -H "Authorization: Bearer $(cat token)" \
     http://$JSON_API_HOST/v1/parties/allocate \
     -d '{}'

You can optionally pass either of (or both) identifierHint and displayName if those are relevant:

curl -XPOST \
     -H "Authorization: Bearer $(cat token)" \
     http://$JSON_API_HOST/v1/parties/allocate \
     -d '{"identifierHint": "hint", "displayName": "display me"}'


I don’t use the JSON API, so I go with the Ledger API.

Would this be correct Java code:

public PartyManagementServiceOuterClass.AllocatePartyResponse alloc(String party, boolean withPartyHint) throws ExecutionException, InterruptedException {
        ManagedChannel channel = ManagedChannelBuilder.forAddress(host, port).usePlaintext().build();
        var stub = PartyManagementServiceGrpc.newFutureStub(channel);

        PartyManagementServiceOuterClass.AllocatePartyResponse response;
        if (withPartyHint){
            response = stub.
        } else {
            response = stub

        return response;

How do I send a JWT token here?


You need to call stub.withCallCredentials and pass an instance of CallCredential that passes the Authorization header with the Bearer schema. This is the current implementation for it in the Java bindings.