Runtime Keys
Learn how RuntimeHQ separates state metrics between production and non-production channels.
Runtime Keys
A Runtime Key (referred to as runtimeKey throughout our documentation) is required by our SDKs and Runtime APIs to integrate with your applications to consume it's resolved operational state.
The runtimeKey must start with either the rt_prod_ or rt_test_ prefix. This key is uniquely generated for each consuming application and environment. You can find your runtimeKey under the Integration tab of your specific application in the RuntimeHQ Console.
Note
The runtimeKey is a public, read-only identifier. It is entirely safe for client-side exposure in browser environments, as it cannot be used to modify any operational state.
Environment Separation
RuntimeHQ strictly separates state metrics between production and non-production channels. These keys can be obtained for your respective application from the Console → Applications → Integration tab:
- Production keys (
rt_prod_*): Tied to live edge caches and incident control dashboards. - Non-production keys (
rt_test_*): Dedicated for lower environments, testing banners, and preview workflows.
Important
Isolation Constraint: Actions taken on non-production state pipelines never leak or affect live customer integrations, ensuring a safe zone for operational rehearsal events.