---
title: "Get Current"
method: GET
path: "/deployments/current"
tags: ["Deployments"]
---

# Get Current

`GET /deployments/current`

Get the current deployment for the device.

## Response `200`

Successfully retrieved the current deployment.

- Deployment
  - `object` 'deployment', required — The object type, which is always `deployment`.
  - `id` string, required — ID of the deployment.
  - `description` string, required — The description of the deployment.
  - `status` 'drifted' | 'staged' | 'queued' | 'deployed' | 'archived' | 'failed' | 'retrying', required — This status merges the 'activity_status' and 'error_status' fields, with error states taking precedence over activity states when errors are present. For example, if the activity status is 'deployed' but the error status is 'failed', the status is 'failed'. However, if the error status is 'none' and the activity status is 'deployed', the status is 'deployed'.
  - `activity_status` 'drifted' | 'staged' | 'queued' | 'deployed' | 'archived', required — Last known activity state of the deployment. - Drifted: device's configurations have drifted since this deployment was staged, and the deployment needs to be reviewed before it can be deployed - Staged: is ready to be deployed - Queued: the deployment's config instances are waiting to be received by the device; will be deployed as soon as the device is online - Deployed: the deployment's config instances are currently available for consumption on the device - Archived: the deployment is available for historical reference but cannot be deployed and is not active on the device
  - `error_status` 'none' | 'failed' | 'retrying', required — Last known error state of the deployment. - None: no errors - Retrying: an error has been encountered and the agent is retrying to reach the target status - Failed: a fatal error has been encountered; the deployment is archived and (if deployed) removed from the device
  - `target_status` 'staged' | 'deployed' | 'archived', required — Desired state of the deployment. - Staged: is ready to be deployed - Deployed: all config instances part of the deployment are available for consumption on the device - Archived: the deployment is available for historical reference but cannot be deployed and is not active on the device
  - `device_id` string, required — ID of the device.
  - `release_id` string, required — ID of the release.
  - `created_at` string, date-time, required — Timestamp of when the device release was created.
  - `updated_at` string, date-time, required — Timestamp of when the device release was last updated.
  - `config_instances` ConfigInstance[] — The config instances associated with this deployment.
    - `object` 'config_instance', required — The object type, which is always `config_instance`.
    - `id` string, required — ID of the config instance.
    - `config_type_name` string, required — The name of the config type.
    - `filepath` string, required — The file path to deploy the config instance relative to `/srv/miru/config_instances`. `v1/motion-control.json` would deploy to `/srv/miru/config_instances/v1/motion-control.json`.
    - `created_at` string, date-time, required — The timestamp of when the config instance was created.
    - `config_schema_id` string, required — ID of the config schema which the config instance must adhere to.
    - `config_type_id` string, required — ID of the config type which the config instance (and its schema) is a part of.
    - `content` InstanceContent, required
      - `format` 'json', required
      - `data` string, required — The configuration values associated with the config instance.

---

[API](https://skmtc.dev/mirurobotics/apis/miru-agent-api.md) · [All operations](https://skmtc.dev/mirurobotics/apis/miru-agent-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mirurobotics/miru-agent-api/revisions/08bf1f388a66/schema)