---
title: "Proxy a command to remote FPP"
method: POST
path: "/api/remoteAction"
tags: ["remoteAction"]
---

# Proxy a command to remote FPP

`POST /api/remoteAction`

## Request

- Base URL: `/` (relative, and the document was published on a file host, not at the API’s origin)
- URL: `/api/remoteAction`
- Auth: none declared

Proxies a named action to a remote FPP instance by IP address. Supported actions: `listUpgrades`, `reboot`, `restartFppd`, `updateLog` (the remote's running FPP/OS update, with its log tail). `reboot` and `restartFppd` change the remote: send them by POST, which FPP 11 will require of them. The others read and stay GETs. An OS upgrade of another player is a MultiSync job (`streamRemoteJobs.php`, type `upgradeOS`), which streams its progress.

## Other responses

- `400`: Invalid action

## Changes

- **2026-10-19** `eab32b805396`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/falconchristmas/apis/fpp-api/changes/api/remoteAction/post.md)

---

[API](https://skmtc.dev/falconchristmas/apis/fpp-api.md) - [All operations](https://skmtc.dev/falconchristmas/apis/fpp-api/llms.txt) - [OpenAPI document](https://skmtc.dev/falconchristmas/apis/fpp-api/revisions/1b633540718c?raw)