Product feature

Temperature monitoring integrations and API for connected workflows.

KRYOS is built to connect. Use API access, webhooks, and data exports to move monitoring data, alerts, certificates, and review context into the systems your team already uses.

Talk to specialist Request demo

Send temperature alerts, device status, report context, and recalibration reminders to external systems.
Use webhooks to receive operational context back when workflows need a two-way connection.
Extend API endpoints, payloads, and field mappings for project-specific integration needs.

Public API and webhook event

202 accepted

POST /webhooks/kryos/events

Webhook eventREST APIData export


                01
                {
              
                02
                  "event": "temperature.alert.created",
              
                03
                  "occurred_at": "2026-04-20T09:42:18Z",
              
                04
                  "asset": {
              
                05
                    "id": "fridge-03",
              
                06
                    "name": "Pharmacy fridge 03",
              
                07
                    "site": "Madrid cold room"
              
                08
                  },
              
                09
                  "reading": {
              
                10
                    "value": 8.4,
              
                11
                    "unit": "C",
              
                12
                    "threshold_max": 8.0
              
                13
                  },
              
                14
                  "incident": {
              
                15
                    "id": "inc_7J29K",
              
                16
                    "status": "open",
              
                17
                    "review_url": "https://app.kryos.io/incidents/inc_7J29K"
              
                18
                  },
              
                19
                  "certificate": {
              
                20
                    "sensor_id": "sen_1842",
              
                21
                    "recalibration_due": "2028-04-20"
              
                22
                  }
              
                23
                }

Alert created temperature.alert.created

Threshold breach with asset and reading context.

Sensor record certificate.updated

Certificate and recalibration dates stay connected.

External update workflow.status.synced

Ticket, ERP, or QMS references can return to KRYOS.

API and webhook payloads are designed to keep monitoring data, asset identity, incident review, and certificate context connected.

Connect monitoring data to the systems around it

Integrations should make temperature monitoring easier to operate, not create another disconnected data stream. KRYOS exposes the records teams need while preserving the monitoring context behind them.

Integration capabilities

Temperature monitoring API

Access structured readings, device state, assets, incidents, certificates, and report context through API endpoints.

Webhook event delivery

Send alert, acknowledgement, device, certificate, recalibration, and report events to external workflows as they happen.

Data export integration

Move reviewed records into reporting tools, BI workflows, QA folders, or internal dashboards without rebuilding the evidence manually.

Two-way workflow context

Receive external references such as ticket IDs, ERP asset data, QMS review status, or internal workflow state where the project needs it.

Custom endpoints and payloads

Expose new endpoints, adjust fields, or create custom webhook payloads for integration requirements that are specific to your rollout.

From API scope to connected workflow

01. Define the system boundary

Identify whether the external system needs live alerts, readings, asset metadata, certificate status, report exports, or review outcomes.

02. Choose API, webhook, export, or custom integration work

Use REST endpoints for requested data, webhooks for event delivery, exports for reviewed records, and custom integration work where the connection needs more shape.

03. Preserve the connected record

Keep external references tied back to the KRYOS asset, incident, certificate, and reporting history so teams can still review the original context.

Structured event payloads

Webhook payloads include the monitored asset, event type, timestamp, values, thresholds, and review links when relevant.

Authentication and access scope

API access can be scoped to the records and systems involved in the integration rather than opening unnecessary data.

Operational handoff

Events can move into ticketing, QMS, ERP, reporting, or internal tools without asking teams to copy data manually.

Future extension

When the integration surface is not enough, KRYOS can discuss additional endpoints, webhook events, or payload fields.

Temperature monitoring integrations that fit real workflows

A useful integration does more than send data out. KRYOS can adapt field mappings, payloads, event logic, and API coverage so monitoring records fit the ERP, QMS, reporting, or internal platform around them.

ERP and asset systems

Keep asset identity, sites, ownership, and location data aligned with the ERP or asset systems that already define daily operations.

QMS and ticketing workflows

Send temperature alerts and incident updates into quality, maintenance, or ticketing workflows while the original KRYOS record remains available for review.

Reporting and BI layers

Move reviewed readings, incidents, reports, and audit context into BI or reporting tools without rebuilding evidence by hand.

Customer-specific middleware

Support authentication, field mapping, payload transforms, and deployment rules when an internal platform sits between KRYOS and your systems.

Extend the API when the workflow needs it

If standard endpoints or webhooks do not cover the workflow, we can discuss new endpoints, additional events, or payload fields.

New endpoint

Expose the specific record, aggregate, or status view your system needs.

New webhook

Trigger an event when an alert, review step, certificate update, or operational action occurs.

New mapping

Match KRYOS fields to the IDs, names, and statuses used inside your internal system.

Discuss the integration surface your workflow needs

Talk to a specialist if you need API access, webhook event delivery, data export integration, or custom endpoints for ERP, QMS, ticketing, reporting, or internal platforms.