Skip to main content
All CollectionsGetting Started
Why did Shake switch from Client ID to API Keys?
Why did Shake switch from Client ID to API Keys?

It’s better, more flexible, and way more secure.

Shake Typing avatar
Written by Shake Typing
Updated over a month ago

At Shake, we’re always looking for ways to make bug reporting smoother and safer for our users. That’s why we decided to switch from Client IDs to API Keys. API Keys offer more security by letting you set specific restrictions—like limiting access to certain domains, IP addresses, or usage patterns—so there’s far less risk of unauthorized access.

Beyond added security, API Keys also allow more control and flexibility. With this setup, you can better manage how Shake is integrated with your systems and easily monitor usage. Ultimately, switching to API Keys helps us support your projects with the best balance of security and simplicity as we continue to grow and evolve.

Also, you can create and manage multiple API keys, so if one is ever compromised, it’s easy to revoke it and generate a new one. This gives you an extra layer of control and lets you respond quickly if you detect unusual activity.

Did this answer your question?