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).
post/api/hf-auth/refresh-relay
Response
Successful Response
object required
Changes
Changed in 2 of the 26 revisions of this API.11
- ○
endpoint added
endpoint-added
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 14 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲