Virtual staging- preview keys
Release date: 5th November 2025
Virtual staging provides a way of accessing unpublished content and media. It's used for visualizations and content previews, allowing you to retrieve the latest version of content, as well as content that is scheduled to go live on a specified date and time. You can also use virtual staging to retrieve unpublished media.
Previously, in order to control access to a virtual staging environment (VSE), you needed to set up a whitelist to restrict access to a set of IP addresses. In this release we've introduced an alternative authorization method- preview keys.
You now have a choice of authorization methods: to use whitelists, or preview keys.
Preview keysLink copied!
Preview keys are generated by developers using the GraphQL Asset Management API and are associated with an organization and a VSE. A preview key is included in the "x-api-key" header of a VSE request to authorize access to content or media.
You can create preview keys within your own code, or by using the GraphQL playground. An example query showing information about a preview key, including its expiry date, whether it's enabled, and the VSE it's associated with, is shown in the image below.
For more information about creating and managing preview keys see the preview keys page.
Client side signingLink copied!
Signed URLs provide a secure way of authorizing access to content and media in a VSE from client side code. While preview keys work seamlessly with server side integrations, in order to keep the keys secure they should not be used in client side requests.
Using the signing service, developers can create a signing key from an existing preview key. This signing key is used to create parameters which are used to sign client side requests for content and media.
The client side signing functionality provides developers with the tools to build their own service to generate signed URLs, and for Amplience to be able to authorize a signed URL. You will need to create a service to manage URL signing.
Visit the client side signing page to find out more.