Authentication
The Recover Software API uses OAuth 2.0 bearer token authentication
Welcome to our guide on managing API credentials, which will provide access to Apkudo's Recover Software API. These API credentials are OAuth2-based, which provides secure delegated access to your resources.
Protecting your API credentials is of utmost importance. Below you'll find detailed steps on how to perform these tasks and a few tips on security.
- Store Safely: Always store your API credentials securely. Do not share them publicly or
expose them in client-side code in a Source Code Repository. - Limit Access: API Credentials are bound to the end user generating the key, take this
into account for your long term implementation plan. Consider creating a service account
for long-term automation. - Secrets can only be viewed at time of generation, you must save the information
immediately after generating the credentials and keep them in a safe location. - You can regenerate your API Credentials at any time, however this will immediately
revoke your previously-generated credentials. - Please be aware of these implications and have a key rotation policy in place for any
automated systems.
The API uses OAuth 2.0 bearer token authentication, which means you need to send a bearer access token in the Authorization header with each HTTP request.
Please refer to the API Reference for more information on how to properly authenticate your API calls.
Updated 11 months ago