You may accidentally delete one or more of your API keys. This can happen when you delete a user, because doing so causes their associated API keys to disappear.
You can restore either deleted or expired keys, but Algolia only keeps the last 1,000 deleted keys.
When you restore a deleted API key, Algolia automatically resets its validity limit to 0 (unlimited).
Using the API
You can restore a key with the restoreApiKey method.
1 | $client->restoreApiKey("myAPIKey"); |
1 | client.restore_api_key('myAPIKey') |
123 | client.restoreApiKey('myAPIKey').then(() => { // done}); |
1 | client.restore_api_key('myAPIKey') |
1 | client.RestoreApiKey("myAPIKey"); |
1 | client.restoreApiKey("myAPIKey"); |
1 | res, err := client.RestoreAPIKey("myAPIKey") |
123 | client.execute { restore key "myAPIKey"} |
Using the Algolia dashboard
You can also restore API keys in your Algolia dashboard with the following steps:
- Go to your dashboard’s API keys section.
- Click the All API Keys tab.
- Click the Restore API Key button, insert your API key, then click Restore.
FAQs
Deleting an API key is irreversible. Before deleting an API key, make sure you no longer use the integration that requires it or that you've replaced it with a new API key. If you delete an API key that is still being used, you'll experience integration failures.
How do you reset API keys? ›
Resetting your own API key
- Sign in to your Prod environment's Site Factory Management Console.
- In the top menu, click your username.
- Click API Key in the menu to display your API key.
- Click Regenerate, and Site Factory will immediately regenerate your API key.
Deleting an API key is irreversible. Before deleting an API key, make sure you no longer use the integration that requires it or that you've replaced it with a new API key. If you delete an API key that is still being used, you'll experience integration failures.
How do I get a new API key? ›
Create API keys
- Go to the Google Maps Platform > Credentials page. Go to the Credentials page.
- On the Credentials page, click Create credentials > API key. The API key created dialog displays your newly created API key.
- Click Close. The new API key is listed on the Credentials page under API keys.
There are many factors and actions that API key management encompasses:
- Cataloging API keys.
- Creating new keys.
- Giving credentials and restrictions to certain keys.
- Adding key authentication to existing APIs.
- Updating applications to support new keys for a particular API.
- Maintaining general API security.
You can change an existing API key and its access and refresh token lifetime values. To change an existing CAM REST API key: In CAM Administrator, select Tools > User Policies and Authentication > REST API Keys. In the Manage REST API Keys dialog box, select the key you want to change, then select Change.
How do I regenerate my Google API key? ›
Go to the Google Maps Platform > Credentials page. On the Credentials page, click Create credentials > API key. The API key created dialog displays your newly created API key.
What should you never do with your API key? ›
- Always use a unique API key for each team member on your account. ...
- Never deploy your key in client-side environments like browsers or mobile apps. ...
- Never commit your key to your repository. ...
- Use Environment Variables in place of your API key. ...
- Use a Key Management Service.
Deleting your API key is simple. Just head over to the API key page and select the trashcan icon next to the API key you'd like to delete. Please note that deleted API keys cannot be used. This may halt any applications you have running using this API key.
How many times can you use an API key? ›
You can use the same API key for multiple websites, or you can generate a new key for each site. You can generate up to 500 unique API keys.
Yes, you can! Whether you have an Unlimited plan or a one-time plan with available credits, you can use a single API Key on as many websites as you want.
How do I check my API key? ›
To find an API key, you usually need to visit the website or platform that offers the API you want to use. The process can vary depending on the specific API provider, but you typically need to sign up for an account, create a project or application, and then generate an API key within that project.
How long does an API key last? ›
API keys are generally not considered secure; they are typically accessible to clients, making it easy for someone to steal an API key. Once the key is stolen, it has no expiration, so it may be used indefinitely, unless the project owner revokes or regenerates the key.
Where is the API key stored? ›
Storing an API key as an environment variable keeps it from being revealed if the source code gets uploaded to a public repository. Developers can also store API keys in secure files outside the application's source tree or use a secrets management service.
What is the secret manager for API key? ›
Secret Manager is a secure and convenient storage system for API keys, passwords, certificates, and other sensitive data. Secret Manager provides a central place and single source of truth to manage, access, and audit secrets across Google Cloud.
What are the risks of API key? ›
Embedding API keys in code: This dangerous practice can unintentionally reveal your API keys to the public, especially if your code is shared on platforms like GitHub. If your code is accessible, so are your API keys, making them vulnerable to misuse by malicious actors.
How do I fix my API? ›
To troubleshoot this API error, start by verifying that the URL is correct. It's also important to check the API documentation to make sure that you're using the correct data parameters with your requests. Finally, contact your API provider for further assistance if all else fails.
Should I delete my API key? ›
It's good practice to create an API key with minimal privileges for one precise and exclusive purpose and delete this API key from the Coveo organization when it's no longer needed for that purpose. You can't undo an API key delete operation.
Why my API key is not working? ›
API keys have multiple dependencies that can result in errors like: "The user is not authorized for this operation based on …". Please make sure you are using the correct credentials and endpoint with the correct API key. For example, your production API key is only able to make calls to the API production endpoint.
How often should API keys be changed? ›
It is recommended to rotate API keys every 90 days. Because of these potential risks, Google recommends using the standard authentication flow instead of API Keys. However, there are limited cases where API keys are more appropriate.
