List of methods
|Create secured API key||
Generate a secured API key without any call to Algolia’s servers.
|Add API key||
Add a new API Key with specific permissions and restrictions.
|Update API key||
Replace every permission of an existing API key.
|Delete API key||
Delete an API Key.
|Restore API key||
Restore a deleted API key, along with its associated rights.
|Get API key permissions||
Get the permissions of an API key. When initializing the client using the admin API key, you can request information for any of your application’s API keys. When using a non-admin API key, you can only retrieve information for this specific API key.
|List API keys||
Get a list of API keys.
|Get secured API key remaining validity||
Retrieve the remaining validity of a secured API key in seconds.
We released a new version of the PHP API client in public beta. Read the beta documentation for more information.
We released a new version of the Java API client in public beta. Read the beta documentation for more information.
Difference between adding and generating (secure) API keys
You can create new API keys in two different ways:
The differences are:
Add API keyruns on Algolia’s servers;
Generate Secured API keyruns on your own server.
- Added keys appear in the Algolia dashboard; generated keys don’t.
- You add keys that are fixed and have very precise permissions. They’re often used to target specific indices, users, or application. They’re also used to generate secured API keys.
You should generate secured API keys when building mobile applications with Algolia.