Skip to main content

​
About Revivn

Revivn is an IT asset disposition platform for recovering, tracking, and repurposing hardware. Serval connects with OAuth 2.0 client credentials (Client ID and Client Secret). Serval exchanges them for short-lived access tokens at https://api.revivn.dev/oauth/token and refreshes tokens automatically. All API traffic goes to api.revivn.dev. Authentication: OAuth 2.0 client credentials. Revivn does not use a static API key for the REST API. Data sync: On-demand only. Serval calls Revivn when a workflow runs.
This integration is in beta.

​
What the Revivn integration enables

Anything in the Revivn API documentation can be reached through Serval.

​
Get your credentials

Create an OAuth application in the Revivn app and copy the Client ID and Client Secret.
1

Open API credentials in Revivn

Log in to the Revivn app, then go to API → API Credentials.
2

Create an application

Click Create Application, enter a name (for example “Serval”), and save.
3

Copy Client ID and Client Secret

Copy both values immediately. You may not be able to view the secret again after you leave the page.
Store the Client Secret securely when it is shown. If you lose it, create a new application in Revivn and update Serval.

​
Connect in Serval

1

Open the Revivn connect form

Add a new Revivn connection from Serval’s integrations page.
2

Enter instance name

Instance Name is a label for this connection in Serval (for example “Production Revivn”).
3

Enter OAuth credentials

Paste the Client ID and Client Secret from Revivn. Do not use API key mode for a custom application — Revivn expects OAuth bearer tokens.
4

Connect

Submit the form. Serval runs health checks automatically after a successful connect.

​
Verifying the connection

Serval ships four health checks:
  • Test Connection — lists one page of assets. Success: “Successfully connected to the Revivn API.” Failure: “Unable to connect to Revivn. Verify your Client ID and Client Secret from Revivn App → API → API Credentials.”
  • List Assets — confirms read access to /api/v1/assets.
  • List Pickups — confirms read access to /api/v1/pickups.
  • List Asset Retrievals — confirms read access to /api/v1/asset_retrievals.

​
Gotchas and troubleshooting

Re-enter valid Client ID and Client Secret on the Revivn connection in Serval. If the connection was set up as a custom application with an API key instead of OAuth, switch to the catalog Revivn integration and connect with OAuth credentials.
Datadog and other early adopters sometimes used a custom application with the wrong auth type (X-Api-Key). The catalog Revivn integration uses OAuth client credentials and automatic token refresh. Prefer the catalog integration for new setups.