WorkVivo Integration

1. API Token  

2. WorkVivo ID

3. Tenant

4. Domain (.com or .us)

  • We need to get read access to the API token for all public spaces that the client wants us to crawl in our system.

  • We need confirmation from the client on whether they support the .us or .com domain.

  • The tenant is used to build the URL for documents and articles that we need to get it from the client.

------------------------------------------------------------

Get an Access Token

Note: to create an app and generate an access token you must have the Developer role.

āš ļø Warning: Granting a user the Developer role allows them to create API Apps. Those Apps can be given permissions, up to and including Admin permissions so make sure you trust a user before granting them this role. Please be aware that developers may have the ability to perform actions through the Customer API that your organisation restricts in the user interface.

  • Navigate to https://workvivo.com/admin/developers/apps/manage

  • Take note of your Organisation Id. You will need to pass this as a Workvivo-Id header for all requests.

  • Create a new app. Select which permissions your app needs. You can change this later. We recommend only giving the minimum set of permissions needed.

  • Click on Manage Keys for your App. Create a new API key and copy the Token.

  • Paste your Token into your Authorization header. Don't forget to include Bearer before the token in the header.

For Legacy API docs please click here.

AUTHORIZATIONBearer Token

This folder is using Bearer Token from collection Workvivo Developers

Was this article helpful?