Skip to main content
This is the v3 quickstart. New integrations should use the v4 quickstart, which authenticates with OAuth 2.0.

Getting Started

To interact with the Zivio API, you first need to create an API key within your Zivio platform. You can find out how to do this is in the following section.

Creating an API Key

First, navigate to the ‘Admin’ tab in your navigation menu, and click on ‘Admin Dashboard’. There you will see a list of options, as in the image below: Admin Dashboard Click ‘API Keys’, which will take you to the below screen: API Keys Click ‘Add API Key’, and you will be presented with the screen below. Type a name that will help you identify your API Key, and click the ‘Create’ button. New API Keys You will be redirected back to the ‘API Keys’ page when your new key has been successfully created. Note the flash message that appears: New Api Key Flash Please note down the token value, as you will need it when making requests in the next section.

Making an Example Request

Before making a request to the Zivio API, make sure you have noted down your token value.
To learn how to retrieve your API Key token value from the platform, please see the Creating an API Key section above.
When making a request, set your token value in the X-API-Key header:

Where to send the request

There are two ways to reach the v3 API. The regional API endpoints — these are the URLs listed in the API Reference and used by its playground: These endpoints serve every Zivio organisation, so each request must also identify yours with the zivio-tenant-id header. Ask your Zivio administrator for your organisation identifier.
A request to a regional endpoint without a valid zivio-tenant-id returns 404 Tenant Unknown. This is checked before authentication, so it is not a problem with your API key.
Your own Zivio domain — if you send requests to your organisation’s own Zivio URL instead, the organisation is already identified by the hostname and the zivio-tenant-id header is not required.
For more information, including the structure of the response for each endpoint, please see the api-reference section.