canton-network-docs
Ledger API Errors
Ledger API Errors - Canton Network Docs
Skip to main content
Cause: The bearer token is missing, malformed, expired, or signed with an unrecognized key.
Fix:
Cause: The validator does not have the DAR that contains the referenced package, or the package has not been vetted.
Fix: Upload the DAR:
After uploading, confirm the package appears in the package list before retrying the command.
Cause: The party identifier in the command does not match any party allocated on this validator.
Fix: Allocate the party first, or verify you are using the correct party identifier. Party IDs are case-sensitive and include a fingerprint suffix (e.g.,
Cause: The authenticated user does not have rights to act as the requested party.
Fix: Grant the user read/write access to the party through the Admin API:
These gRPC status codes come from the Ledger API layer.Documentation Index
Fetch the complete documentation index at: https://docs.canton.network/llms.txt
Use this file to discover all available pages before exploring further.
AUTH_INVALID_TOKEN
- Verify the token has not expired (check the
expclaim) - Confirm the token audience matches
LEDGER_API_AUTH_AUDIENCE - Ensure the token includes the
daml_ledger_apiscope - Check that the JWKS URL configured on the validator is reachable and returns the correct signing keys
PACKAGE_NOT_FOUND
PARTY_NOT_KNOWN
Alice::1220abcd...). List known parties: