Overview
We’ve improved how legacy v1 API keys are managed to reduce the risk of stale credentials and support the move to Private Integration Tokens (PIT).
Legacy API keys that have been unused for more than 90 days are now automatically marked as Expired. This applies to both platform-level and Location-level keys. Active keys are not affected.
If an expired key is still needed, it can be made usable again by rotating or refreshing it. New v1 key creation is no longer supported, and PIT should be used for any new credentials going forward.
What’s included?
- Automatic expiration for legacy v1 keys inactive for more than 90 days
- Support for both platform-level and Location-level keys
- Ability to restore expired keys through rotation or refresh
- Removal of new v1 key creation
- Email notifications for keys nearing expiration
- Recommendation to use Private Integration Tokens (PIT) for new credentials
Why it matters?
This update improves security by reducing exposure from unused legacy credentials and helps standardize new integrations on PIT.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article