POST /accounts/{account_id}/intel/sinkholes
Create a new sinkhole. Logs of large request bodies will be truncated, but the full request body can be recorded in R2. If you wish to record large request bodies in R2, include the R2 key ID, key secret, and bucket name in the request body.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
account_id |
String | Yes |
The unique identifier for the Cloudflare account. |
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 |
|---|---|---|---|
r2_bucket |
String | No |
The name of the R2 bucket to store results. Required if you want to store large request bodies in R2. |
r2_id |
String | No |
The id of the R2 instance. Required if you want to store large request bodies in R2. |
name |
String | Yes |
The name of the sinkhole. |
r2_secret |
String | No |
The secret key for the R2 API token. Required if you want to store large request bodies in R2. |
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.