---
name: appid-api-reference
title: Regions and endpoints
description: You can use the IBM Cloud® App ID APIs for DevOps automation, customization, and management of your service instances. To understand availability of the service, you can review the following connectivity options.
last-updated: 2026-03-04
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/appid?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Regions and endpoints
{: #regions-endpoints}

You can use the IBM Cloud® App ID APIs for DevOps automation, customization, and management of your service instances. To understand availability of the service, you can review the following connectivity options.
{: shortdesc}


## Available regions
{: #available-regions}

App ID is available in the following regions:

![Visual representation of the availability of the service. The image is a map with pin points in the locations in which the service is available. If you are unable to view this image, see the table in the service endpoints section for a complete list.](images/regions.svg){: caption="App ID availability" caption-side="bottom"}

This image is an artistic representation and does not reflect actual political or geographic boundaries.
{: note}


## Service endpoints
{: #service-endpoints}

If you're managing your service instances of App ID programmatically, see the following table to determine which API endpoints to use when you connect to the APIs.

| Region | Endpoint  |
|--------|-----------|
| Dallas | `us-south`|
| Frankfurt | `eu-de` |
| London | `eu-gb` |
| Osaka | `jp-osa` |
| Sao Paulo | `br-sao` |
| Sydney | `au-syd` |
| Tokyo | `jp-tok` |
| Toronto | `ca-tor` |
| Washington | `us-east` |
{: caption="Lists public endpoints for interacting with App ID APIs" caption-side="top"}



## Formatting your API call
{: #format-call}

Calls to the management API endpoint take the following structure:

```sh
https://<regionEndpoint>.appid.cloud.ibm.com/management
```
{: codeblock}

| API | Endpoint  |
|--------|-----------|
| Authorization | `https://<region>.appid.cloud.ibm.com/oauth/v4`|
| Management | `https://<region>.appid.cloud.ibm.com/management/v4`|
| Profiles | `https://<region>.appid.cloud.ibm.com/api/v1` |
{: caption="Formatting for the available APIs" caption-side="top"}