.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp)
.png?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.png?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp){kind=icon}
Limitations of Delivery Tokens
- The number of Delivery Tokens is restricted based on your Contentstack subscription plan. To increase this limit, contact Contentstack support.
- A Delivery Token can be linked to all branches and aliases in a stack or restricted to just one branch or alias. Associating a token with a specific set of branches or aliases is not supported.
- Tokens don’t automatically expire, so unused tokens may remain active indefinitely.
- Delivery Tokens are read-only tokens. To manage content, you must use Management Tokens instead.
- Only the stack Owner, Admin, and Developer roles have permission to create Delivery Tokens.
Was this article helpful?
More articles in "Work with Delivery Tokens"
