API Application Control Change

During 2023, we improved the security of Provet Cloud APIs by updating our API authorization method. We are transitioning from API keys to OAuth 2.0, a recognized industry standard, which makes online authorization easier and safer.

Currently any new integration should not start using API keys. They are still available only for integrations that have been live before this migration started. If you need API keys, please contact Provet Cloud support. 

The goal is to revoke all existing API keys. This applies to sandbox environments as well. Even if you are not yet live with your integration, you should switch to OAuth 2.0 if someone has created you API key to your sandbox. 

Developer TODO List

  1. Read about new Provet Cloud API settings on Provet Cloud Support page. You can see examples how to use OAuth also in our developer documentation
  2. Contact our support and ask for OAuth credentials to your sandbox environment by filling this form
  3. Change your integration to use OAuth 2.0 instead of API keys and test it in the sandbox environment.
  4. When you are ready to go live, contact us again by making a support ticket. Tell us:
    1. What is the name of your integration template that needs to go live
    2. Who are the customers using your integration and what are their Provet Cloud ids.
  5. Support will then make your integration template public and add the integration application to those Provet Cloud tenants that use your integration. You will automatically receive their authorization information.
  6. You can then add the client information to your integration and go live with the version using OAuth 2.0.

We are here to help you! If you have any questions, submit a request for our support team.


Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.