Request limits
Kivra handles millions of documents and applies request limits to protect the service and distribute system resources fairly. These limits also help reduce head-of-line blocking and provide a consistent experience for recipients.
The limits below are subject to change. An endpoint-specific limit takes precedence over the default payload limit.
Content size
Section titled “Content size”The complete JSON object for one content delivered to one recipient must be
less than 1 MB. This includes all embedded files. For example, if you embed
two PDFs in JSON content sent to a user, the combined JSON object must be
smaller than 1 MB.
If the JSON includes a responsive_part, then the content limit is increased
to 2 MB to allow space for the HTML file.
Rate limit
Section titled “Rate limit”You can send up to 50 contents to the same recipient per minute. You can send
more than 50 contents per minute overall when they are distributed across
different recipients, but no recipient may receive more than 50 contents in
one minute.
Design high-volume integrations to distribute deliveries over time and across recipients.
Payload size
Section titled “Payload size”Unless an endpoint specifies otherwise, requests have a maximum payload size of
10 MB. Kivra rejects a request larger than this limit with HTTP 413 Payload Too Large.
For example, recipient matching requests can contain up to 10 MB of data. See Recipient matching for the endpoint-specific request formats.