POST /networks/{id}/actions/add_subnet
Adds a new subnet to the Network.
If the subnet ip_range is not provided, the first available /24 IP range will be used.
If a change is currently being performed on this Network, a error response with code conflict will be returned.
Servers
- https://api.hetzner.cloud/v1
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
Integer | Yes |
ID of the Network. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
type |
String | Yes |
Type of subnet.
Possible values:
|
network_zone |
String | Yes |
Name of the Network Zone. The Location contains the |
vswitch_id |
Integer | No |
ID of the robot vSwitch. Must be supplied if the subnet is of type |
ip_range |
String | No |
IP range of the subnet. Uses CIDR notation. Must be a subnet of the parent Networks Must not overlap with any other subnets or with any destinations in routes. Minimum network size is /30. We highly recommend that you pick a larger subnet with a /24 netmask. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.