Hello TP-Link Team,

I am trying to integrate my Omada Controller with Zabbix using the OpenAPI v2, but I always get the following error when querying sites or devices:

{"msg":"Controller ID not exist.","errorCode":-7131}

Steps I did:

1. Created an OpenAPI client in Omada Controller (Client Credentials mode).

2. Successfully obtained an access token via:

   /openapi/authorize/token?grant_type=client_credentials

3. Verified that token is valid (otherwise I would get -44116).

4. When calling sites or devices endpoints:

   GET /openapi/v2/sites?omadacId=<OmadaID_from_UI> GET /openapi/v2/sites/{siteId}/devices?omadacId=<OmadaID_from_UI>

   I always get -7131 Controller ID not exist.

What I tried:

• Using the OmadaID shown in the UI → fails.

• Using the controllerId seen in /api/info → same error.

• Even tried the serverKey found in logs → still -7131.

• Tried passing omadacId as query param, JSON body, and X-OmadacId header → all fail.

My Goal:

Monitor my EAP115 and ER605 devices (status, rxBytes, txBytes) via Zabbix using the Omada OpenAPI.

Question

• Which value should be passed as omadacId in the v2 API endpoints on Controller v5.15.24.18?

• Is there a known issue with OpenAPI -7131 on this version?

• Is there a workaround or patch available?