- Overview
- Tutorials
- How Tos
- Download
- Install
- Configure
- Secure
- TLS API Configuration
- Configure API Authentication and Authorization with JWT
- Configure API Limits
- Set Resource Limits
- Crypto key management
- Restrict key usage
- Namespace Key Management
- Key management service (KMS) configuration
- Optimize
- Observe
- Operate
- Initializing node identity manually
- Canton Console
- Synchronizer connections
- High Availability Usage
- Manage Daml packages and archives
- Participant Node pruning
- Party Management
- Party Replication
- Decentralized party overview
- Setup an External Party
- Ledger API User Management
- Node Traffic Management
- Identity Management
- Upgrade
- Decommission
- Recover
- Troubleshoot
- Explanations
- Reference
Note
This page is a work in progress. It may contain incomplete or incorrect information.
Configure API Limits¶
Max Inbound Message Size¶
The APIs exposed by both the participant (gRPC Ledger API and Admin API) as well as
by the synchronizer (Public API and Admin API) have an upper limit on incoming message
size. To increase this limit to accommodate larger payloads, the flag
max-inbound-message-size
has to be set for the respective API to the maximum
message size in bytes.
For example, to configure a participant’s gRPC Ledger API limit to 20MB:
canton.participants.participant2.ledger-api {
address = "127.0.0.1"
port = 5021
max-inbound-message-size = 20971520
}