Was this article helpful?
Thanks for your feedback
Delivery Tokens are tokens that provide you with read-only access to the associated environments. It is a credential—used along with the stack API key—to make authorized Content Delivery API requests for retrieving the published content of an environment.
Note: The delivery token can be assigned to all the branches or to a specific branch. You can also assign it to all the aliases or a specific alias, to fetch data from their associated branches. Refer to our Global Modules document for more information.
By default, Contentstack does not provide any delivery tokens. You need to create new tokens for the environments of your stack.
You can use one token to fetch content from only one environment. This means that you need to create different tokens for different publishing environments of your stack.
Having separate tokens for different environments ensures that only the specified people have access to the content of the required environments. For example, testers can fetch content of only the “staging” environment, while content managers have access to the “production” environment. This separation ensures the safety of your content and allows you to manage separate delivery channels independently.
Key points to remember:
- You can associate a delivery token with only one environment. Consequently, you need to create different tokens for different environments.
- Delivery tokens can be used to fetch only published content, not unpublished or draft content.
- You can create a maximum of 20 tokens in a stack.
To get further understanding on Delivery tokens, make sure you read our documentation in the “More articles” section
