Step by Step Guide: Admins & IT - Hive Open API
.Category: Open API | Type: Step-by-step guide | Part 2 of 2 in : Open API
π‘ New to this feature? To understand more about the User Data Uploader and how to prepare your file, see [Link to page
What you'll find in this guide:
The Open API is configured in two stages: an admin in Hive creates a service account and generates an API key, then an IT or data analyst connects that key to their BI tool.
Checklist
|
β |
Check |
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
|
|
β |
Step-by-Step Upload Walkthrough
π© [Any call outs or warnings HERE]
[ADD IN STORYLANE IF AVAILABLE]
Part 1: admin setup
Step 1 - Create a service account
A service account is not a person β it has no password and cannot log into Hive. It's a named account your API key is attached to, so you can identify where requests are coming from and manage access cleanly.
- Go to Settings and select Service Accounts
- Click Create service account
- Give it a descriptive name β for example, PowerBI Dashboard or HR Analytics Team β and save
You can create multiple service accounts, one per tool or team. Each can have its own API keys with different permission sets.
Step 2 - Generate an API key
- From the Service Accounts page, click on the account you just created (or select Manage API keys)
- Click Create API key
- Select the permissions for this key β these control which data types it can access. If you're unsure, you can grant full access initially and restrict later
- Click Create, then copy the API key immediately and store it in a secure location
βΌοΈImportant: API keys are shown only once at creation. If you navigate away without copying it, you will need to generate a new one. Store your key in a password manager or secure vault before closing the window.
Once created, the key will be listed under the service account with details including who created it, its permissions, creation date, and expiry date. Keys expire after 90 days and each key is rate-limited to 200 requests per minute.
Part 2: Connecting to your BI tool
This section is for the IT or data analyst completing the integration.
Step 1 - Open the API documentation
Before building any integration, use Hive's built-in API documentation to explore endpoints and test requests live in your browser.
- From the Service Accounts page, click View API docs
- Enter your tenant slug β this is the subdomain of your Hive URL (e.g. if your URL is yourcompany.hive.hr, your slug is yourcompany)
- Paste your API key into the Authentication field β the documentation will use it automatically for all test requests in that session
Note: If you refresh the browser, you will need to re-enter your tenant slug and API key. They are not saved between sessions.
Step 2 - Test your connection
Each endpoint in the documentation has a Test request button. Use this to check what data looks like before writing any integration code.
- A 200 status means the request was successful
- A 401 status means unauthorised β usually an incorrect or missing API key
Step 3 - Connect to Power BI
- In Power BI for example, select Get Data > From Web
- Paste the Hive endpoint URL (e.g. api.hive.hr/v1/heatmap/{survey_id})
- When prompted for authentication, select Web API or Advanced and enter your API key as an HTTP request header: Authorization: Bearer [Your_Key]
- Use Power Query to clean and shape the response β Hive returns flattened JSON to minimise transformation work
Step 4 - Build your first view
Once connected, use the Attributes endpoint first to retrieve segment IDs, which you'll need to filter data in all other endpoints. Then use the Surveys endpoint to retrieve survey IDs for pulling scores, metrics, and Key Drivers.
Available endpoints
|
# |
Endpoint |
What it returns |
When to use it |
|
1 |
List attributes & segments |
All demographic attributes, segment IDs, and date buckets |
Run first β IDs here are needed to filter all other requests |
|
2 |
List surveys |
Survey name, type, status, start/end date |
Use to find the survey ID for other endpoints |
|
3 |
List survey questions |
All questions in a survey, with type and options |
Use to identify question IDs for the statistics endpoint |
|
4 |
Get question statistics |
Response count, average score, distribution, favourable scores |
Detailed per-question analysis |
|
5 |
List metrics |
Engagement Index, eNPS, average score, custom metrics |
Headline metrics; filterable by segment or date |
|
6 |
Get Key Drivers |
Driver questions, influence scores, coefficients, action labels |
Understanding what's driving (or hindering) engagement |
|
7 |
Get heatmap data |
Flat list of scores by question and segment |
Building custom heatmap visualisations |
|
8 |
Get response facets |
Available segments, buckets, and demographic filter options |
Check which filters exist before making filtered requests |
|
9 |
List Open Door submissions |
Anonymous feedback text, filterable by date and segment |
Feeding qualitative data into sentiment or NLP tools |
|
10 |
List Hive Fives |
Peer-to-peer recognition events with recipient and sender attributes |
Mapping recognition trends and cross-department collaboration |
Monitoring with API Logs
Every request made through the Open API is logged and visible to any user with the Administrator of Integrations role.
- Go to Settings and select API Logs
- Each entry shows: the endpoint called, the API key used, the parameters passed, the response status, and a link to the response data
API Logs are useful for monitoring usage patterns and debugging if something isn't working as expected.
API Logs are useful for monitoring usage patterns and debugging if something isn't working as expected.
Troubleshooting Common Errors
If something goes wrong, here are the most common issues and how to fix them.
|
Error / Issue |
Likely cause |
How to fix it |
Frequently Asked Questions
[Add any FAQs that will support the customer throughout this guide]
|
β Previous Back to Open API Overview |
End
|
π Other Useful Information
π
Require further technical assistance? Contact Our Support Team