---
title: "API Gateway prerequisites"
slug: "apigw-spec"
tags: ["API Gateway"]
updated: 2026-09-17T09:17:40Z
published: 2026-09-17T09:17:40Z
canonical: "guide.ncloud-docs.com/apigw-spec"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Gateway prerequisites

Available in Classic and VPC

Check supported environment, limitations, and usage fee for best usage of API Gateway.

## Cloud environment specifications

The cloud environment specifications supported by API Gateway are as follows:

| Item | Specifications |
| --- | --- |
| Region (Zone) | Korea, U.S. West, Singapore, Japan, and Germany |
| Platform | VPC, Classic |
| Languages | Korean, English, and Japanese |

              Note

              

For more information on the VPC environment, see [Service introduction](https://www.ncloud.com/product/networking/vpc) on the NAVER Cloud Platform portal, and for more information on whether the VPC environments are supported for each service, see [Ncloud user environment guide](/docs/en/environment-environment-1-1).

## Limitations

The limitations of API Gateway are as follows:

- APIs registered with API Gateway can only be called via HTTPS.
- Communication with the endpoint server supports both HTTP and HTTPS.

## Pricing information

API Gateway fees are calculated based on a combination of API call fees, network traffic, and cache usage.

              Note

              

If you designate NAVER Cloud Platform service as the endpoint, additional network fees may apply.

For more information on API Gateway usage fees, see pricing information on **Services > Application Services > API Gateway** on the portal.

- [**Portal > Services > Application Services > API Gateway**](https://www.ncloud.com/product/applicationService/apiGateway)