Cloud-Based Omada Controller Open API: No Interface Access Address Available

Hello TP-Link Team,

I am trying to integrate my application with an Omada Cloud-Based Controller using the Open API and Client Credentials authentication mode.

I previously encountered the following error when attempting to request an access token:

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

After receiving guidance to refer to the latest Omada Controller v6.3 API documentation, I reviewed the official guide “How to Create Site in Omada Controller via Open API.”

The guide states that under:

Global View → Settings → Platform Integration → Open API

I should record both:

• Omada ID

• Interface Access Address

and use the Interface Access Address when calling the Open API.

However, I have a Cloud-Based Controller and I cannot find a public/cloud Interface Access Address.

The only address available to me appears to be the controller's private LAN address, which I cannot communicate with from my application environment.

My situation is:

• Controller type: Omada Cloud-Based Controller

• Controller is accessible through the Omada Cloud portal

• Controller status: Online

• Open API application: Created and enabled

• Authentication mode: Client Credentials

• Omada ID: Available in the Open API configuration

• Client ID and Client Secret: Available

• Interface Access Address: No cloud/public address visible

• Only a private/LAN address appears to be available

• The private LAN address is not reachable from my application environment

I previously tested regional cloud API hosts manually, including the EU regional endpoint, but encountered either:

403 CloudFront
This distribution is not configured to allow the HTTP request method that was used

or:

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

Based on the latest documentation, I now understand that I should not guess the API host and should instead use the Interface Access Address provided by the controller.

However, for my Cloud-Based Controller, I cannot locate that Interface Access Address.

Could you please clarify the following:

1. Where can I find the Interface Access Address for an Omada Cloud-Based Controller?

2. Does the Cloud-Based Controller provide a public Open API endpoint, or is Open API access only available through a private/LAN interface?

3. If the controller is accessible through the Omada Cloud portal, is there a supported API endpoint that external applications should use?

4. Is the Interface Access Address intentionally hidden or unavailable for Cloud-Based Controllers?

5. Does Open API Client Credentials authentication work for Cloud-Based Controllers the same way it works for Hardware and Software Controllers?

6. If only a private LAN address is available, what is the recommended architecture for an external backend application that needs to communicate with the controller?

7. Is there any additional Cloud Access, VPN, network configuration, or controller setting required before the Interface Access Address becomes available?

I would appreciate guidance on the correct supported endpoint and authentication flow for a Cloud-Based Omada Controller.

Thank you.