---
canonical: https://amplience.com/developers/docs/apis/limits/
title: Limits
description: Usage limits for Amplience products and API, including limits for Dynamic Content APIs and general usage of Dynamic Content app, limits for Content Hub and limits for Workforce.
audience: Developer
date_published: 2022-08-26
date_modified: 2026-05-28
---
# Limits
On this page we've included the various limits for the Dynamic Content APIs and general system limits.
Note that most of these limits are hard coded and cannot be changed. Generally you should not be close to these limits.
## API limits
### HTTP Content Delivery API
| Feature | limit | Description |
| :------------------------- | :---------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Delivery Keys | 150 characters maximum. | 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. |
### GraphQL Content Delivery API
| Feature | Limit | Description |
| ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Request size | `8KB ` | If a request exceeds this limit, the query will not be run and an error will be returned. |
| Response size | `1MB ` | If a request exceeds this limit, the query will not be run and an error will be returned. |
| Complexity score | `1000` | The complexity score limit for a query is 1000. If a query exceeds the complexity score limit, the query will be ended, and an error will be returned. |
### Filter API
The following limits apply to the `trait:filterable` and `trait:sortable` sections of content type schemas.
#### trait:filterable
| Feature | limit | Description |
| :------------------------ | :------------- | :----------------------------------------------------------- |
| filterBy paths | 5 | Up to 5 filterBy paths can be included in a filterable trait |
| Entries in filterBy paths | 5 | Up to 5 entries can be included in a filterBy path |
| filterBy path entry | 128 characters | The maximum length of an entry in a filterBy path |
#### trait:sortable
| Feature | limit | Description |
| :---------------------- | :------------- | :------------------------------------------------------- |
| sortBy paths | 3 | Up to 3 sortBy paths can be included in a sortable trait |
| Entries in sortBy paths | 5 | Up to 5 entries can be included in a sortBy path |
| sortBy key | 128 characters | The maximum length of a sort key |
#### Other limits
| Feature | limit | Description |
| :--------------- | :----------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------- |
| Page size | 12 if `depth` is between 1 and 22 | The maximum number of items that can be returned in one page of a response. The request timeout is 10 seconds. |
| Page size | 50 if `depth=0` or no `depth` is specified | The maximum number of items that can be returned in one page of a response. The request timeout is 1 second. |
| Complexity limit | 500 items | This refers to the number of content items involved in processing a request. If the limit is exceeded, a 524 error is returned |
### Hierarchies
| Feature | limit | Description |
| :------------------- | :----- | :--------------------------------------------------------- |
| Hierarchy tree depth | 15 | 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 |
> **Note: Maximum nodes in a hierarchy branch**
> Hierarchy drag and drop is currently supported for branches containing up to 200 nodes.
### Dynamic Content Management API
#### Rate limits
| Feature | limit | Description |
| :--------------------------------------------- | :----------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API requests | 5000 requests per minute | This limit is enforced as standard. We reserve the right to introduce a lower rate limit |
| Publish/ Unpublish content requests | 100 requests per minute | This rate limit applies to Dynamic Content Management API requests that publish content and unpublish content (the limit is publish and unpublish requests combined) |
| Bulk publish/ Publish hierarchy nodes requests | 10 requests per minute | This limit is per account and is shared between the Dynamic Content Management API and the Dynamic Content app |
**_Also see [API rate limits](https://amplience.com/developers/docs/apis/limits/#api-rate-limits)._**
### GraphQL Asset Management API
#### Rate limits
| Feature | limit | Description |
| :----------- | :--------------------- | :------------------------------------------------------ |
| API requests | 60 requests per minute | Tracked against the API keys assigned to your media hub |
**_Also see [API rate limits](https://amplience.com/developers/docs/apis/limits/#api-rate-limits)._**
#### Other limits
| Feature | limit | Description |
| :--------------- | :----------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------- |
| Complexity limit | A complexity limit of `10000` points is applied per request. | See [how the complexity limit is calculated](https://amplience.com/developers/docs/apis/asset-management/overview/limits/#complexity-limits) |
#### Temp file service
| Feature | limit | Description |
| :-------------------------------- | :---- | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Single part file upload file size | 100MB | The maximum size of files that can be uploaded using a [single part upload](https://amplience.com/developers/docs/apis/asset-management/temp-file-service/#using-the-api) |
| Multi part upload file size | 2GB | The maximum total size of a file that can be uploaded using [multi part upload](https://amplience.com/developers/docs/apis/asset-management/temp-file-service/#using-multi-part-upload) |
### Virtual staging
#### Rate limits
Limits when requesting unpublished content and media using the Content Delivery and Media Delivery APIs with a virtual staging environment (VSE).
| Feature | limit | Description |
| :------------------------- | :---------------------------------------------------------------------- | :---------------------- |
| Content and media requests | 7 requests per second with a burst (bucket fill rate) of 350 per minute | This limit is enforced. |
**_Also see [API rate limits](https://amplience.com/developers/docs/apis/limits/#api-rate-limits)._**
> **Info: VSE rate limit notes**
> - These limits are applied separately to each VSE in your account.
> - When using multiple modes ([latest, timestamp and snapshot](https://amplience.com/developers/docs/dev-tools/guides-tutorials/virtual-staging/virtual-staging-dynamic-content/#dynamic-content-and-virtual-staging)) of VSE, the limit is shared across all VSE modes for a given VSE.
> - Limits are applied separately for content and media using the same VSE.
### Fresh API
The Fresh API uses the same format of requests and responses, and is subject to the same limits, as the Content Delivery v2 API and Filter API. There are also some additional rate limits:
#### Rate limits
| Feature | limit | Description |
| :----------- | :---------------------------------------------------------------- | :--------------------------------------------------- |
| API requests | 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](https://en.wikipedia.org/wiki/Exponential_backoff).
**_Also see [API rate limits](https://amplience.com/developers/docs/apis/limits/#api-rate-limits)._**
### Content rendering service
| Feature | limit | Description |
| :------------------------------------- | :--------------------------------- | :------------------------------------------------------------------------------------------------------------ |
| Response size | The maximum response size is 64 MB | This is the size of the HTML response |
| Maximum handlebars template size | 64 KB | The maximum size of an individual handlebars template. An error `500` will be returned |
| Maximum number of handlebars templates | 50 | The maximum number of distinct handlebars templates that can be invoked as a result of a single request is 50 |
| Maximum number of partials | 1000 | The maximum number of partials that can be loaded as a result of single request |
### API Rate limits
In addition to the rate limits specified, 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.
## System limits
This section outlines general limits, for example, limits applicable to using Dynamic Content, Content Hub and Workforce.
### Webhooks
| Feature | limit | Description |
| :----------------------------- | :------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------ |
| Custom payload | The maximum size of the custom payload is 5 KB | This is the handlebars template that defines the custom payload |
| Webhook request | The maximum size of the custom payload output is 200 KB | This is the output size when the custom payload is processed. |
| Webhook request headers | 7 KB | This is maximum size of all headers combined |
| Webhook request retry attempts | 11 | The maximum number of retry attempts for HTTP requests. The maximum duration for retries is 13 hours |
| Custom payload retry attempts | 5 | The maximum number of retry attempts when creating a custom payload. The maximum duration for retries is 15 minutes |
### Search
| Feature | limit | Description |
| :----------------------- | :------ | :-------------------------------------------------------------- |
| Search index record size | 100 KB | The maximum size of a record stored in a search index is 100 KB |
| Search analytics data | 90 days | The length of time search analytics data is stored |
### Content type schemas
| Feature | limit | Description |
| :-------------- | :----- | :-------------------------------------------------------------- |
| Schema size | 100000 | The maximum size of a content type schema is 100000 characters |
| Schema URL size | 950 | The maximum size of a content type schema URL is 950 characters |
### Snapshots
Snapshots are an immutable representation of a content item. Snapshots are generated when:
- A content item snapshot is saved to an edition or content is added to a slot in an edition
- Content is published
- Editions are scheduled
- Editions are previewed
| Feature | limit | Description |
| :------- | :--------- | :---------------------------------------- |
| Snapshot | 2500 items | The maximum number of items in a snapshot |
### Dynamic Content usage
| Feature | limit | Description |
| :------------------------------------- | :---- | :----------------------------------------------------------------------------- |
| Maximum number of hubs | 100 | The maximum number of hubs per account |
| Maximum number of repositories | 500 | The maximum number of repositories per account |
| Maximum number of repositories per hub | 100 | The maximum number of repositories in an individual hub |
| Content item statuses | 100 | This is the maximum number of content item statuses that can be added to a hub |
| Edition slots | 200 | Up to 200 slots can be added to an edition |
| Content versions | 2300 | The maximum number of versions for a content item |
| Locales per hub | 100 | Up to 100 locales can be added to a hub |
| Delivery keys per content item | 100 | A content item can have up to 100 variant delivery keys |
### Content sync
| Feature | limit | Description |
| :----------------------------------------- | :------ | :-------------------------------------------------------------- |
| Maximum number of active jobs | 1 | The maximum number of jobs that can be run at a time, per organization |
| Maximum number of content graphs in a job | 20 | The maximum number of content items (content graphs) that can be included in a sync job |
| Maximum number of items in a content graph | 15,000 | Maximum number of items supported per content graph |
| Maximum number of content items that can be synced per calendar month | 1000 | To increase the number of content items you can sync per month, please contact your Account Manager|
### Content hub and apps
| Feature | limit | Description |
| :--------------------- | :------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Asset manual upload | 100 MB | The maximum size files that can be uploaded with a manual upload |
| Number of folders | 10,000 | Each Content Hub user can have a maximum 10,000 folders across all of the asset stores to which they have access |
| FTP upload | 30 | The maximum number of simultaneous open connections per host/ IP address is 30. There is a limit of 100 total connections per account.
We recommend closing an FTP connection when you have completed an upload.
Amplience reserves the right to change these limits to ensure service availability for all our customers |
| Media share size limit | 1000 MB | The maximum size of a single share |
### Dynamic Media
| Feature | limit | Description |
| :--------------- | :------------------- | :---------------------------------------------------------------- |
| Image request | 8,000 x 8,000 pixels | The maximum dimensions for an image requested from Dynamic Media. |
| Video resolution | 4096 x 4096 | This is the maximum resolution at which video can be encoded |
### Workforce
#### Workforce extension limits
| Feature | limit | Description |
| :---------------------------- | :------------------- | :---------------------------------------------------------------- |
| Number of extensions | 50 | The maximum number of extensions per hub |
| Number of extension actions | 50 | The maximum number of actions an extension can have |
| Number of extension instances | 100 | The maximum number of extension instances allowed per hub (also known as 'installed' extensions)|
#### Workforce custom template limits
| Custom template limits | Description |
| :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
| Maximum number of custom templates | The maximum number of custom templates per hub is **150** |
| Number of text components per template | The maximum number of text components (Single-line text field, Multi-line text field and Rich text editor) per custom template is **10** |
| Number of table components per template | The maximum number of table components per custom template is **5** |
| Number of image components per template | The maximum number of image components per custom template is **1**. Each image component can contain up to 5 images |