Data & Integrations
The Data & Integrations tab is every way data leaves PRIZM Cloud. It holds three cards: a CSV export, your company’s API credentials, and your webhooks.
This page covers creating and managing all three. For what PRIZM Cloud actually sends and how your server should answer, see the Webhook reference and REST API.
Export data
Download the values your devices have recorded as a CSV, one column per device field.
Pick a Start Date and an End Date
The end date must be after the start date and not in the future. The range defaults to the last 24 hours.
Choose which Device Fields to include
The selector defaults to All fields — leave it empty and the export includes every field the company has defined. Select one or more fields to export only those columns, which is faster and produces a smaller file when you only need a handful of fields out of a much larger set.
Your selection is remembered per company, so it carries over to your next export. Open the dropdown and click Clear all filters to go back to exporting every field.
Click Export Data
Three limits worth knowing before you pick a wide range:
- Large exports are slow and the file is large. There is no progress indicator beyond the button state.
- One export at a time per company. Starting a second while the first is still running fails. If a colleague is mid-export, wait.
- The form does not stop you asking for data that no longer exists. A range reaching back past your retention window returns nothing for the part that has expired, with no warning — see Data retention.
What the file looks like
The first four columns are always time, companyId, deviceId, and bundleId. After that comes one
column per device field, named after its Identifier and sorted alphabetically. One row per value received,
numbers and booleans written as-is and text written unquoted.
A company with temperature and humidity fields, exported with All fields, produces a CSV that
opens like this:
| time | companyId | deviceId | bundleId | humidity | temperature |
|---|---|---|---|---|---|
| 2026-09-28T14:32:10Z | uuid | uuid | uuid | 41 | 22.5 |
| 2026-09-28T14:31:10Z | uuid | uuid | uuid | 22.1 |
The second row’s device didn’t report humidity at that timestamp — a missed reading is an empty
cell, not a zero.
Selecting Device Fields removes the column entirely, it doesn’t just blank it. Exporting the same range
with only temperature selected produces this instead:
| time | companyId | deviceId | bundleId | temperature |
|---|---|---|---|---|
| 2026-09-28T14:32:10Z | uuid | uuid | uuid | 22.5 |
| 2026-09-28T14:31:10Z | uuid | uuid | uuid | 22.1 |
humidity is gone, not blank — there’s no way to tell from this file that the field exists.
Company API Key
Your API key is what your own applications authenticate with. Copy API Key to Clipboard copies it; the Company ID shown below the buttons has its own copy button beside it.
You need both for different things: the key authenticates requests, and the
Company ID identifies your company in payloads and support tickets. Webhook
payloads include it as companyId.
There is one key per company. Every employee and every application shares it.
See REST API for how to send it.
Reset the company key
Reset Company Key issues a new key and invalidates the old one.
Resetting the key takes effect immediately and breaks every application still using the old one. There is no grace period, no overlap window, and no second key to fall back on — every backend, script, and third-party service authenticating with the old key fails until someone pastes in the new one. Reset it if you think the key has leaked; otherwise leave it alone.
Webhooks
A webhook is a URL PRIZM Cloud calls with a POST as field values arrive, so your
own systems can react without polling.
Click Create Webhook
Enter a Name and a URL
The name is for you. The URL must be a valid URL, and should be HTTPS.
Add any Headers you need
Each header is a key and a value, added a row at a time with Add Header. Use these for whatever your endpoint needs to authenticate the call — PRIZM Cloud sends whatever you put here and nothing more.
Click Test Webhook
This fires a real request at the URL in the form and reports what came back.
Click Save Changes
Three things about this form are easy to miss:
- The limit is three webhooks per company. At three, the button reads FULL and is disabled. Delete one to make room.
- Test Webhook uses the values in the form, not the saved ones. You can test a URL before you save it, and you can test an edit before committing it.
- Editing and deleting live in the table. Each row’s Action menu has Edit Webhook and Delete Webhook.
For the payload shape, the retry behaviour, and what your server should return, see the Webhook reference.
Who can manage integrations
Everything on this tab requires the Owner or Admin role. Employees with the User role have no access to Settings at all — it does not appear in their sidebar. Full table: Who can do what.