On this page we've included the various limits for the Dynamic Content APIs and general usage of the Dynamic Content app. Limits for Content Hub and apps are also included.
Note that most of these limits are hard coded and cannot be changed. Generally you should not be close to these limits.
Must conform to validation rules and be unique on a hub
Get multiple content items
12 items in the request
The combined maximum of either delivery keys or ids
Nested content
22 levels
The content graph of a content item may be nested up to a depth of 22 levels. If you are close to this limit, you may consider using content references instead of content links.
Content item body size
200 KB
The maximum size of the content item body.
Request time limit
10 seconds
The maximum time allowed before a request times out.
The number of levels that can be added to a hierarchy
Hierarchy item limit
10,000
The total number of items that can be added to a hierarchy
Node children limit
500
The number of children that can be added to a node
API Rate limits
In addition to the rate limits shown below, Amplience reserves the right to impose rate limits on requests to our APIs. We will only do this to help guarantee service availability to all our customers.
The Fresh API uses the same format of requests and responses, and is subject to the same limits, as the Content Delivery 2 API and Filter API. There are also some additional rate limits:
100 requests per second. Burst limit: 200 requests per second
This rate limit applies to requests to the Fresh API
Requests to the Fresh API are tracked against the API keys assigned to your hubs. Each of these API keys has a rate limit associated with it. Exceeding the rate limit will result in 429 responses from the service. When receiving a 429, your code should attempt a retry after delaying the next request with exponential back-off.