CaliberOS integrations

CaliberOS API & webhooks.

Build calibration into the tools your team already uses. The public calibration software API, webhook delivery, and developer docs are pilot-launch targets and are not available in the current app.

Live at pilot launch All integrations

How it would work.

  • Endpoint summary

    The intended public endpoints cover three resources: assets (look up instruments and due dates), calibration events (read completion dates and results), and certificates (retrieve approved certificate metadata and links when available). Public paths and access scopes will be confirmed in the pilot documentation.

  • Webhook events

    The first example event is calibration.completed. Candidate additions include asset.updated, calibration.due_changed, and certificate.issued. These names and payload fields are illustrative, not a published contract.

  • How HMAC signing is intended to work

    The sender uses a shared secret to sign the raw payload. A receiver verifies that signature before processing the event, and should reject a failed verification or stale replay. The pilot docs will specify the header, signing input, retry policy, and how to deduplicate deliveries.

Developer preview

An example webhook event.

This illustrative payload shows what a calibration completion event might send. It is not a live endpoint or a published payload contract.

calibration.completed · example
{
  "event": "calibration.completed",
  "asset_tag": "TRQ-0089",
  "result": "pass",
  "as_found": {
    "value": 49.62,
    "unit": "N·m",
    "in_tolerance": true
  },
  "certificate_url": "https://app.caliberos.io/c/8f2k-41",
  "next_due": "2026-12-14",
  "drift": {
    "predicted_oot": "2027-03-22",
    "suggested_interval_mo": 9
  }
}

FAQ

Frequently asked questions

Can I use the public API today?

No. The current signed-in app uses an internal API. The developer API, documentation, and outbound webhooks are targeted for pilot launch.

What can a webhook tell me?

The sample shows a calibration result, instrument tag, certificate link, and next-due date. Use it to discuss your workflow, not as a production payload specification.

How will webhook recipients verify a delivery?

The planned design signs each delivery using HMAC. The receiver verifies the signature against its shared secret before processing the event.

Tell us what you need to connect.

Join the waitlist and tell us which workflow you’d like to pilot.

Join the waitlist