EIPGROUP IP count upgrade
Updated at：2025-10-16
- Used to specify EIPGROUP IP count upgrade
Request structure
Plain Text
1PUT /v{version}/eipgroup/{id}?{action}&clientToken={clientToken} HTTP/1.1
2Host: eip.bj.baidubce.com
3Authorization: authorization string
4
5{
6 "eipAddCount": eipAddCount,
7 "eipv6AddCount": eipv6AddCount
8}Request headers
No special headers beyond common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number, current value is 1. |
| id | String | Yes | URL parameter | EIPGROUP ID |
| action | String | Yes | Query | Operations on EIPGROUP instance, with the value resize taken in this API |
| clientToken | String | Yes | Query | Idempotence token, for details, refer to [clientToken](EIP/API Reference/General Description.md#Idempotence) |
| eipAddCount | int | No | RequestBody | The number of newly added IPv4 EIPs in the EIPGROUP package. The value must exceed 0, and the maximum count of Public IPs can reach {n} (with {n}*5Mbps needing to remain below the EIPGROUP capacity). |
| eipv6AddCount | int | No | RequestBody | The number of newly added IPv6 EIPs in the EIPGROUP package must be greater than 0. The maximum count of Public IPs is governed by quota control, with a default limit of 1,000. |
At least one of eipAddCount or eipv6AddCount must be provided, meaning you must increase either IPv4 or IPv6 counts when using the IP count upgrade API.
Response Status Code
Respond with 200 after successful operation, and respond with error codes after failed operation, as shown in [Error Codes](EIP/API Reference/Error code.md)
Response headers
No special headers beyond common headers.
Response parameters
There are no special response parameters
Request example
Plain Text
1PUT /v1/eipgroup/eg-b2511000?resize&clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1
2HOST eip.bj.baidubce.com
3Authorization bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2016-04-10T08:26:52Z/1800/host;x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02
4
5{
6 "eipAddCount": 1,
7 "eipv6AddCount": 1
8}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 946002ee-cb4f-4aad-b686-5be55df27f09
3Date: Wed, 10 Apr 2016 08:26:52 GMT
4Transfer-Encoding: chunked
5Content-Type: application/json;charset=UTF-8
6Server: BWS