> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Invalidate calibrations

This guide details how to mark [calibrations](https://docs.mirurobotics.com/cfg-mgmt/concepts/calibrations.md) invalid through the Miru Agent's [Device API](https://docs.mirurobotics.com/developers/device-api/overview.md).

## Overview

By default, all calibrations are valid when they're reported.

However, calibrations can stop being valid, for example when a power cycle moves a component out of calibration. On-device applications can mark a component's latest calibration invalid using the [invalidate latest calibration](https://docs.mirurobotics.com/references/device-api/latest/endpoints/calibrations/invalidate-latest.md) endpoint in the Device API.

Once a calibration is invalidated, it cannot be marked valid again. Instead, simply [report a new calibration](https://docs.mirurobotics.com/cfg-mgmt/report-calibrations.md) for that component, which is valid by default, and the dashboard shows the latest calibration for that component as valid again.

## Prerequisites

To follow this guide, you must have a device installed with a Miru Agent [v0.13.0](https://docs.mirurobotics.com/changelog/agent.md#v0-13-0) or later, and call Device API [v0.3.0](https://docs.mirurobotics.com/changelog/device-api.md#v0-3-0) at `/v0.3`. With the Python Device SDK, use `v0.11.0` or later.

## Invalidate a calibration

Calibrations are invalidated via the [invalidate latest calibration](https://docs.mirurobotics.com/references/device-api/latest/endpoints/calibrations/invalidate-latest.md) endpoint in the Device API. Only a component's latest calibration can be invalidated.

When a calibration is invalidated, the agent marks it invalid on the device and immediately returns a `200` response, regardless of whether the device is online or offline. Once a device is online, the agent uploads the invalidation to Miru, which sets the calibration's [invalidated at](https://docs.mirurobotics.com/cfg-mgmt/concepts/calibrations.md#param-invalidated-at).

### Required parameters

To invalidate a calibration, the following parameters are required:

**component** `string` *required*

The [slug](https://docs.mirurobotics.com/cfg-mgmt/concepts/components.md#param-slug) of the component whose latest calibration to invalidate.

Example: `kuka-arm`

**reason** `string` *required*

Why the calibration is no longer valid. Free text, at most 512 characters, and not blank.

Example: `power cycle`

The agent invalidates the component's latest calibration at the time of the call.

### Optional parameters

In some cases, you may want to invalidate a specific calibration instead of whatever the latest resolves to be. To do so, send the `report_id` of the calibration to invalidate.

**report\_id** `string`

The report ID of the calibration to invalidate, as read from the [list latest calibrations](https://docs.mirurobotics.com/references/device-api/latest/endpoints/calibrations/list-latest.md) endpoint. If it isn't the component's latest calibration, the agent invalidates nothing.

Example: `0b6f3c2e-6a51-4e0f-9a43-2f1d7c9e8b10`

The agent invalidates the calibration only while it's still the component's latest, so a calibration reported in the meantime isn't marked invalid by mistake.

## Response

The agent responds with `200 OK` and the invalidated calibration:

```json nocopy theme={null}
{
  "object": "calibration",
  "report_id": "0b6f3c2e-6a51-4e0f-9a43-2f1d7c9e8b10",
  "component": "kuka-arm",
  "serial_number": "SN-1234",
  "reported_by": "Jane Doe",
  "reported_at": "2026-03-10T12:00:00Z",
  "invalidated_at": "2026-03-11T08:00:00Z"
}
```

If the calibration is already invalid, the agent returns it unchanged. So a calibration keeps the time of its first invalidation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.