spectator81-png

spectator81-png / omada-api-toolkit

Public

Unofficial Node.js client & docs for the undocumented TP-Link Omada Controller Web API v2. Zero dependencies. Reverse-engineered from browser DevTools.

acl api firewall homelab network-automation
13
3
69% credibility
Found Feb 27, 2026 at 11 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
JavaScript
AI Summary

Unofficial toolkit offering a simple Node.js script to automate management of TP-Link Omada controllers for tasks like networks, WiFi, and firewall rules.

How It Works

1
🔍 Discover the toolkit

You're managing your home or office network with a TP-Link Omada controller and want an easy way to automate setups like WiFi networks or security rules.

2
📥 Get the simple helper file

Download the single ready-to-use file from the project page—no extra installations needed.

3
✏️ Add your controller details

Type in your controller's web address and your login name and password so it knows where to connect.

4
🚀 Connect and explore

Run the file once and it links up to your controller, showing you lists of your devices, networks, and current rules right away.

5
🛠️ Make changes easily

Use the built-in examples to create new WiFi spots with custom zones, add safety rules between areas, or tweak access point settings.

✅ Network runs smoothly

Everything is set up just how you like it, saving you time from clicking through web pages every time you need adjustments.

Sign up to see the full architecture

4 more

Sign Up Free

Star Growth

See how this repo grew from 11 to 13 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is omada-api-toolkit?

This unofficial Node.js client lets you automate TP-Link Omada controllers via their undocumented Web API v2, reverse-engineered straight from browser DevTools. It handles the quirky triple-auth flow—controller ID, CSRF token, session cookie—and exposes helpers for VLANs, SSIDs, firewall ACLs, AP channels, and mDNS rules. Zero dependencies means you drop it in any JavaScript project and start scripting with a single connect() call.

Why is it gaining traction?

Unlike the official OpenAPI v1, which skips VLANs, SSIDs, and port profiles, this fills the gap with exact payloads, pitfalls docs, and ready examples—no guesswork on cryptic errors. Devs dig the raw apiCall() for any endpoint discovered in DevTools, plus zero-deps simplicity over bloated unofficial Node.js clients on GitHub. It's like those reverse-engineered APIs for controllers that just work out of the box.

Who should use this?

Network engineers scripting Omada deployments for VLAN provisioning or AP overrides. Home labbers automating SSID creation with VLAN tags or firewall rules between trusted and IoT nets. DevOps teams integrating Omada into CI/CD for switch ports and channel tweaks, skipping the UI entirely.

Verdict

Grab it if you're deep in Omada automation—docs and examples punch above the 10 stars and 0.699999988079071% credibility score. Still early; test on OC220 firmware 6.x and contribute PRs for broader hardware. Solid starter over reinventing auth from scratch.

(187 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.