Skip to main content
You connect Omada once at the MSP level, with an Open API application on your Omada cloud controller: its Interface Access Address, Omada ID, Client ID and Client Secret.

​
1. Create the Open API application

1

Pick the view

Sign in to your Omada cloud controller as an administrator. To reach all your Omada customers, stay in the MSP view. To reach one organization’s sites, open that organization’s Global view.
2

Create the application

Open Settings > Platform Integration > Open API and add an application in Client mode. Give it a role that can manage the customers and sites Neo should reach.
3

Copy the values

Click View on the application and copy the Interface Access Address, the Omada ID (in the MSP view it is your MSP ID), the Client ID and the Client Secret.
Changing the application’s role, site or customer privileges, or copying or importing sites, makes Omada cancel the tokens it issued. Neo then gets a new token by itself. Deleting the application, or creating a new secret, stops Neo until you save the new values here.

​
2. Add the application in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → TP-Link Omada, under Networking.
2

Save the application

Pick the account type (MSP view or Single organization), paste the Interface Access Address, Omada ID, Client ID and Client Secret, and click Save settings. Neo checks them against Omada before saving, so a wrong value is rejected straight away.
After you save, Neo maps your Omada customers (MSP view) or sites (single organization) to the companies in your PSA. Check and correct the matches on the Organization Mapping tab.

​
3. Turn Omada on per agent

1

Open the agent's integrations

Open the agent in the Neo Dashboard and go to its Integrations tab.
2

Pick an access profile

Under TP-Link Omada, pick an access profile, or set each permission group by hand.
The TP-Link Omada API page lists every permission group and the changes that always ask a technician.

​
Limits

  • Neo connects to the Omada cloud controller only. A self-hosted Software Controller or an OC hardware controller cannot be connected.
  • Neo cannot upload or download files (firmware images, backups, certificates, exports), run batch calls, transfer the controller’s owner or change its cloud account binding.