API Keys
Copy the Token for the environment you are in, replace a Token or a Secret, and know what each replacement breaks.
Configure > API Keys holds the two credentials of the environment named in the top row. Switch between Development and Production there, and this page follows.
Before you start
- Every Product has exactly two environments, Development and Production. They share one setup and keep user, company and event data apart.
- Replacing a credential is admin only. Members read the page and copy the Token.
Setting it up
Copy the Token. The Token is what your snippet carries, and it is public: it appears in your page source. Development admits any site. Production admits only sites under a verified Domain.
Replace the Token. Confirm, and the current Token stops working at once. No session opens in that environment until your deployed code carries the new one.
Replace the Secret. The Secret signs identity verification from your server, and it is shown once, when it is created or replaced. Copy it before you close the screen: we do not keep it in a form anyone can read back. Your pages are unaffected.
What it changes
- The previous Secret keeps verifying for 24 hours after you replace it, so you can deploy without rushing. End that window early on Identity verification.
- A replaced Token has no such window.
- Each environment's data stays with it. Replacing a credential deletes nothing.
A Secret is shown once. If you lose it, nobody can recover it: replace it and deploy the new one.
When it goes wrong
Nothing arrives although the snippet is live. Your code is carrying the other environment's Token. Copy the one on this page and verify it on Installation.
Signatures fail after you replaced the Secret. The 24-hour window has passed and your server still signs with the old value. Replace the Secret again and deploy the new one.