---
title: "Set Robot Display Name"
method: POST
path: "/api/daemon/robot-name"
---

# Set Robot Display Name

`POST /api/daemon/robot-name`

Persist a new robot display name and apply it live (no restart).

Persists the name to disk, then refreshes the advertised copies so the
rename takes effect immediately: the daemon status + central relay (via
``Daemon.apply_robot_name``) and the LAN mDNS record. This is the REST
entry point used by the BLE setup service; the WebRTC ``set_robot_name``
command goes through the same live-apply path on the backend.

## Request body

- RobotNameRequest — Body for setting the robot display name.
  - `name` string, required

## Response `200`

Successful Response

- RobotNameResponse — The robot's current display name (``null`` only if none is resolvable).
  - `name` string, nullable

## Other responses

- `422` — Validation Error

## Changes

- **2026-07-27** `1b79de8eefb7` — 1 info
  - endpoint added
- **2026-07-27** `478204bd59f9` — 1 breaking
  - api path removed without deprecation
- **2026-07-24** `69db2d0ea45e` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/pollen-robotics/apis/reachy-mini-rest-api/changes/api/daemon/robot-name/post.md)

---

[API](https://skmtc.dev/pollen-robotics/apis/reachy-mini-rest-api.md) · [All operations](https://skmtc.dev/pollen-robotics/apis/reachy-mini-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pollen-robotics/reachy-mini-rest-api/revisions/7f5f936a81cc/schema)