An API key pasted into a script for last year's event, then forgotten, is still a way into your event data. Now every new key gets an expiration date, Studio shows when each key was last used, and keys that sit idle for a year switch themselves off.

What's new

Choose how long a key lives

When you create a key, pick its Expiration date: 7 days, 30 days, 60 days, 90 days (the default), 1 year, or Custom to set an exact date.

See every key's status at a glance

The API Keys list now shows, for each key, when it was created, when it was last used, and when it expires, or that it already has. Spotting a key that hasn't been used in months takes a second.

Unused keys expire on their own

A key that hasn't been used for 12 months expires automatically. Events run on yearly cycles, so a key nobody has called in a year is almost always a forgotten one. This applies to existing keys too, including those created without an expiration date.

A heads-up before anything breaks

You get an email shortly before a key expires, and another once it has: enough time to swap the key in your integration before anything stops syncing. Expired keys stay in the list, marked as expired, but they can't be turned back on. Create a new key and update your integration.

How to create a key

1. In Studio, open API Keys and click Create a new key.
2. Give it a Key name and choose an Expiration date.
3. Click Generate the key, then copy it right away: for security reasons, it's only shown once.