Introduction

Dedicated Gateway

Dedicated gateways are billed based on the gateway edition and public outbound access bandwidth. For details, see Table 1 and Table 2.

For details about gateway editions, see Product Specifications. For details about gateway edition prices, see Pricing Details.

Pay-per-use: a postpaid mode, in which you can use APIG first and then pay the bills based on the usage duration. The fees are calculated by second and settled by hour. This mode allows you to adjust resource usage easily. You do not need to prepare resources in advance, and will not have excessive or insufficient preset resources. This mode is suitable for scenarios with traffic bursts, such as e-commerce.

**Table 1** Billing modes of the gateway edition
Billing Mode	Pay-per-use
Payment Mode	Postpaid Billed by your gateway edition and actual usage duration
Billing Cycle	Billed by second and settled by hour
Billing Item	Gateway specifications
Stopping Billing	Billing stops after the gateway is deleted.
Specifications Change	Supported
Scenario	Recommended if API demands fluctuate. You can enable and delete resources whenever necessary.

If your API backend service is deployed on the public network, you will be charged for the bandwidth for forwarding API requests to the public network in addition to the gateway fee.

If your backend service is deployed in the same Virtual Private Cloud (VPC) as your dedicated gateway, the backend service can be accessed using a private IP address. You do not need to purchase bandwidth for the gateway.
If your dedicated gateway contains APIs that will be called from the public network, you need to purchase an Elastic IP (EIP) and bind it to the gateway.
If the APIs in your dedicated gateway will be called within the VPC, you do not need to purchase or bind an EIP to the gateway.

**Table 2** Billing mode of the public outbound access bandwidth
Billing Mode	Pay-per-use
Payment Mode	Postpaid Billed by the bandwidth and usage duration
Billing Cycle	Billed by second and settled by hour
Billing Item	Public outbound access bandwidth
Bandwidth Change	Supported
Scenario	Suitable for APIs whose backend services are deployed on the public network.

Shared Gateway (Old Console)

The shared gateway on the old console is billed based on the number of API calls you have received and the amount of data transferred over the public network. For details, see Table 3.

The shared gateway on the old console has been removed and is available only for existing users. For details about the billing mode, see Pricing Details.

**Table 3** Billing mode of the shared gateway (old console)
Billing Mode	Pay-per-use
Payment mode	Postpaid Billed for what you use.
Billing cycle	By day. Bills are generally issued within 1 to 3 hours after the current billing cycle ends.
Billing items	Usage (including the number of API calls and the amount of data transferred over the public network) If you use APIG in conjunction with backend services that are in different regions or offered by other cloud service providers, additional charges may be incurred for data transfer from APIG to the backend services.
Scenario	Suitable for scenarios with a small number of API calls.