---
title: "Refresh Relay"
method: POST
path: "/api/hf-auth/refresh-relay"
---

# Refresh Relay

`POST /api/hf-auth/refresh-relay`

Force the central signaling relay to reconnect — see ``notify_force_reconnect``.

Response shapes:
  - ``{"status": "requested", "token_available": bool}`` — a
    reconnect was kicked off.
  - ``{"status": "skipped", "token_available": bool,
        "reason": "relay_not_running" | "relay_unavailable"}`` — no
    reconnect happened. The mobile app's auto-heal loop must NOT
    wait for a state change in this case (it would hang forever).
    ``relay_unavailable`` covers the import failure (Lite-only
    build that ships no relay module); ``relay_not_running`` covers
    the module-present-but-no-instance case (daemon started
    without a token / pre-init / shutdown).

## Response `200`

Successful Response

- object

## Changes

- **2026-05-11** `b1a61d4d0d88` — 1 info
  - endpoint added
- **2026-03-03** `8d430e48a90a` — 1 breaking
  - api path removed without deprecation

[Change history](https://skmtc.dev/pollen-robotics/apis/reachy-mini-rest-api/changes/api/hf-auth/refresh-relay/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)