Creating Multiple API Keys with different permissions
I want to be able to create multiple API keys with different access permissions so that I can provide different keys to different external tools.
E.g. one tool would access our data on a read only basis and the second on a read/write basis
The current setup does not allow multiple API keys to be created and only maps the users permissions to the standard API key. This doesn't work for 2 reasons:
- Firstly it is usually the same user who works on the API projects. Therefore it is this person who wants to create and be responsible for all the API keys connecting with third party apps.
- This user is likely going to have a high level of access (given they are a developer) so needs to be able to provide lower access levels within the API keys.
Does anyone have a workaround or is this something that Pipedrive can develop?
Comments
-
Hi @Leo each API token is tied to a specific user and company. Each user user can only have one valid API token at any given time, and no two users have the same token. If any user changes the API token, all existing integrations using that API token will not be able to make successful requests against our API and will stop working.
So the user who will work on API projects can use their personal API token with different external tools. You simply need to make sure this user has all the necessary permissions in Pipedrive to perform the intended API requests.
For the full documentation, please visit the Pipedrive developer area here.0 -
@Manuel Oliveira thanks for your comment but you have not addressed my point.
Which is that I (as the primary user in charge of API) want to give differing levels of API permission to different apps. Therefore I need to be able to create multiple API keys.0 -
Hi @Leo , the only way to achieve that is to have multiple users, each with a different permission level and their personal API key to sync to different apps. Having multiple API keys per user is not planned for the immediate future, but I have passed on your request as product feedback for the team.
0