I was using a generic API key in order to access the PipeDrive API from a server. This server maintains data integrity between our database and our PipeDrive data.
I recently saw this announcement:
As of December 2, 2019 , we will be removing the Authorizations endpoint:
We deprecated this endpoint on February 28, 2019, and we strongly advise you to avoid the use of this endpoint. The /authorizations endpoint is a legacy way of authorization using generic API keys. Such an approach does not provide transparency into which applications have access to data nor the opportunity to control the permissions these integrations have. Therefore we suggest using OAuth Authorization.
In case you are using the /authorizations API endpoint in your code or 3rd party app/integration, please remove any dependency on this endpoint as soon as possible.
Please tell me that there is a way via your new implementation of OAuth that I can get a server based type of Key, just like GMail allows me to do, so that I don’t have to have a user signing in every time the server wants to make a call to the PipeDrive API.