Aruba Central API Gateway Domains by Region

How to identify the correct HPE Aruba Central API Gateway domains by region

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:

Region

API Gateway domain

US-1

app1-apigw.central.arubanetworks.com

US-2

apigw-prod2.central.arubanetworks.com

US-WEST-4

apigw-uswest4.central.arubanetworks.com

EU-1

eu-apigw.central.arubanetworks.com

EU-3

apigw-eucentral3.central.arubanetworks.com

Canada-1

apigw-ca.central.arubanetworks.com

China-1

apigw.central.arubanetworks.com.cn

APAC-1

api-ap.central.arubanetworks.com

APAC-EAST1

apigw-apaceast.central.arubanetworks.com

APAC-SOUTH1

apigw-apacsouth.central.arubanetworks.com

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

    • What are the APIs used for VMware VeloCloud SD-WAN monitoring in Site24x7?

      The table below shows the APIs used for fetching data from the VMware VeloCloud SD-WAN. Replace the hostname in the API URL with the appropriate value according to your VMware VeloCloud SD-WAN. API API details ...

    • Roles supporting tunnel management and path data in VMware VeloCloud SD-WAN

      Introduction In VMware VeloCloud SD-WAN, the ability to create or modify tunnels and view path (tunnel) data depends on the user role. This ensures that configuration changes and diagnostic insights are restricted to authorized users. The table below ...

    • Costing for API Calls in Oracle Cloud Monitoring (OCI)

      When integrating Site24x7 with Oracle Cloud Infrastructure (OCI), metric data is retrieved using the SummarizeMetricsData API. This API is part of OCI monitoring and is used to fetch time series metric data for resources. Understanding how OCI ...

    • Troubleshooting hardware sensor monitoring

      This guide helps you troubleshoot issues related to hardware sensor monitoring across supported network devices. If temperature, voltage, fan, or power sensors are missing, show incorrect status, or fail to report values, this document walks you ...

    • How many API calls does Site24x7 GCP monitor make

      Site24x7 Google Cloud monitoring (GCP) fetches the health and performance metrics and your Google Cloud resources' data via APIs. Here is an illustrative calculation on how many API calls will be made by Site24x7 for monitoring your Google Cloud ...