Introduction

Aruba Central uses region-specific API Gateway domains to handle requests from devices and integrations. When configuring monitoring, integrations, or API access, it is important to use the correct regional domain corresponding to your Aruba Central deployment.

This article lists the supported regions and their respective API Gateway domain endpoints.

Regional API Gateway endpoints

Use the following domain names based on your Aruba Central region:

How to identify your region

To determine your Aruba Central region:

• Check the URL used to access Aruba Central.
• Review your account or tenant details in Aruba Central.
• Contact your Aruba administrator if you're unsure.

When to use these domains

These endpoints are required when:

• Configuring API integrations with Aruba Central.
• Setting up monitoring tools (such as Site24x7).
• Authenticating API requests.
• Troubleshooting connectivity issues.

Using the wrong regional endpoint may result in authentication failures or the inability to retrieve data.

Best practices

• Always match the API Gateway domain with your Aruba Central region.
• Avoid hardcoding endpoints if you're managing multi-region environments.
• Validate connectivity to the domain before configuring integrations.

Related articles

• Add an Aruba Central monitor in Site24x7
• More on Aruba Central monitoring