POST /accounts/{account_id}/magic/ipsec_tunnels
Creates a new IPsec tunnel associated with an account. Use ?validate_only=true as an optional query parameter to only run validation without persisting changes.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
account_id |
String | Yes |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
x-magic-new-hc-target |
Boolean | No |
If true, the health check target in the request and response bodies will be presented using the new object format. Defaults to false. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
customer_endpoint |
String | No |
The IP address assigned to the customer side of the IPsec tunnel. Not required, but must be set for proactive traceroutes to work. |
name |
String | Yes |
The name of the IPsec tunnel. The name cannot share a name with other tunnels. |
description |
String | No |
An optional description forthe IPsec tunnel. |
cloudflare_endpoint |
String | Yes |
The IP address assigned to the Cloudflare side of the IPsec tunnel. |
replay_protection |
Boolean | No |
If Default value: false |
psk |
String | No |
A randomly generated or provided string for use in the IPsec tunnel. |
interface_address |
String | Yes |
A 31-bit prefix (/31 in CIDR notation) supporting two hosts, one for each side of the tunnel. Select the subnet from the following private IP space: 10.0.0.0–10.255.255.255, 172.16.0.0–172.31.255.255, 192.168.0.0–192.168.255.255. |
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.