Tapo-Rest

An unofficial REST (Representational State Transfer) API for controlling and monitoring TP-Link Tapo smart devices such as plugs, strips, bulbs, and cameras.

  • Home Automation
  • Tools & Utilities
An unofficial REST (Representational State Transfer) API for controlling and monitoring TP-Link Tapo smart devices such as plugs, strips, bulbs, and cameras. It exposes real-time telemetry and device-control endpoints to home-automation dashboards and scripts, and ships as a Docker image configured via simple JSON files.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
75last commit 52 days ago
Popular
46197 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
80no serious findings

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
197
Open issues
0
Last commit
2026-09-30
Latest release
v0.5.1
License
Apache-2.0
Activity
stale

Checked 6 days ago - source: GitHub (ClementNerma/tapo-rest)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Unraid AppData Setup Before creating the container, create a folder named tapo-rest-sc in your appdata share. Inside it, create two config files: config.json and devices.json. Refer to the project repository documentation for the required configuration structure. source
  • Configuration Create a JSON configuration file containing your Tapo device credentials before first start; the configuration structure is documented in the repository README. source
  • Initial Configuration Before starting the container, create a JSON configuration file specifying your Tapo device credentials (user, password, and device IP/host); see the project README for the full schema. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should the Unraid appdata folder be prepared for Tapo-rest-sc?

Create a folder named tapo-rest-sc in the appdata share before creating the container. Inside it, add config.json and devices.json, following the repository documentation for the configuration structure.

Does an unofficial Tapo API library alter device behavior in the Tapo app?

No. It enables programmatic interaction with Tapo devices, but it does not change how the devices work with the Tapo app.

Is the Tapo REST API project affiliated with TP-Link or Tapo?

No. It is not affiliated with the Tapo or TP-Link brands and is made as a best-effort for personal use.

Answers sourced from community.tp-link.com, github.com, github.com

Community

Collected 49 days ago - public community threads