> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/api-reference/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/api-reference/zec/vpc-network/border-gateway/describeinterconnectbordergatewayregions.md).

# DescribeInterconnectBorderGatewayRegions

## 1. API Description

This API (DescribeInterconnectBorderGatewayRegions) is used to query the regions and data centers that border gateways under the current account can interconnect with. A border gateway can be bound to a CloudRouter to achieve L3 interconnection between VPCs. This interface returns the list of regions that support this feature, which can be filtered by region ID or data center.

## 2. Input Parameters

The following request parameter list only provides API request parameters.

| Parameter Name | Required | Type   | Description                                                                                                                                                               |
| -------------- | -------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| regionId       | No       | String | <p>Region ID, used to filter by a specified region.</p><p>It can be obtained by calling <a href="/api-reference/zec/location/describeregions.md">DescribeRegions</a>.</p> |
| dcId           | No       | String | Data center UUID, used to filter by a specific data center.                                                                                                               |
| dcCode         | No       | String | Data center code, used to filter by a specific data center.                                                                                                               |

## 3. Output Parameters

| Parameter Name | Type                                                                                  | Description                                                                                                           |
| -------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| requestId      | String                                                                                | <p>The unique request ID, which is returned for each request.</p><p>RequestId is required for locating a problem.</p> |
| regionSet      | Array of [InterconnectRegion](/api-reference/zec/datastructure.md#interconnectregion) | List of interconnect regions.                                                                                         |

## 4. Code Example

{% tabs %}
{% tab title="Example" %}
**1. Query all border gateway interconnection regions.&#x20;**~~**1123232**~~**.**

```json
POST /api/v2/zec HTTP/1.1
Host: console.zenlayer.com
Content-Type: application/json
X-ZC-Action: DescribeInterconnectBorderGatewayRegions
<Common Request Params>

Request:
{}

Response:
{
  "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
  "response": {
    "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
    "regionSet": [
      {
        "regionId": "SEA-Tokyo-A",
        "name": "Tokyo",
        "dataCenter": {
          "dcId": "dc-uuid-xxx",
          "dcCode": "TYO1",
          "name": "Tokyo DC1",
          "cityName": "Tokyo",
          "countryName": "Japan"
        }
      }
    ]
  }
}
```

**2. Filter by region ID.**

```json
POST /api/v2/zec HTTP/1.1
Host: console.zenlayer.com
Content-Type: application/json
X-ZC-Action: DescribeInterconnectBorderGatewayRegions
<Common Request Params>

Request:
{
  "regionId": "SEA-Tokyo-A"
}

Response:
{
  "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
  "response": {
    "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
    "regionSet": [
      {
        "regionId": "SEA-Tokyo-A",
        "name": "Tokyo",
        "dataCenter": {
          "dcId": "dc-uuid-xxx",
          "dcCode": "TYO1",
          "name": "Tokyo DC1",
          "cityName": "Tokyo",
          "countryName": "Japan"
        }
      }
    ]
  }
}
```

**3. Filter by data center code.**

```json
POST /api/v2/zec HTTP/1.1
Host: console.zenlayer.com
Content-Type: application/json
X-ZC-Action: DescribeInterconnectBorderGatewayRegions
<Common Request Params>

Request:
{
  "dcCode": "TYO1"
}

Response:
{
  "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
  "response": {
    "requestId": "T05992D0C-7E8B-4047-B0C0-780F2CD549D3",
    "regionSet": [
      {
        "regionId": "SEA-Tokyo-A",
        "name": "Tokyo",
        "dataCenter": {
          "dcId": "dc-uuid-xxx",
          "dcCode": "TYO1",
          "name": "Tokyo DC1",
          "cityName": "Tokyo",
          "countryName": "Japan"
        }
      }
    ]
  }
}
```

{% endtab %}
{% endtabs %}

## 5. Developer Resources

Zenlayer Cloud API 2.0 integrates [SDKs](/api-reference/api-introduction/toolkit/api-sdk.md)，to make it easier for you to call APIs. More programming languages will be supported.

## 6. Error Codes

The following only lists the error codes related to the API business logic. For other error codes, see [Common Error Codes](/api-reference/api-introduction/instruction/commonerrorcode.md).

| HTTP Status Code | Error Code | Description |
| ---------------- | ---------- | ----------- |