Skip to main content
GET
List DDoS filtering presets

Authorizations

Authorization
string
header
required

Your API key, sent as a bearer token. Create one in the control panel under API Keys, give it only the permissions the integration needs, and copy it when it is created. It cannot be shown again. Each key is restricted to one owned team. The key determines the team for every request.

Path Parameters

server
string
required

The server UUID

Example:

"ecc6f4f1"

Response

The whole set, as a JSON array. There is no envelope and no paging.

id
string
required

The id ID.

Example:

"19cfb2ea-daa8-4693-ad63-9d147b00b8f7"

name
string
required

The name shown to customers.

Example:

"HTTPS"

protocol
string
required

The value of protocol.

Example:

"TCP"

description
string | null
required

An optional description shown to customers.

Example:

"Web traffic on port 443, with TLS handshakes validated before they reach the server."

action
string
required

What the preset does with matching traffic, FILTER or DROP.

Example:

"FILTER"

filter
DdosPresetFilterData · object | null
required

The value of filter.

Example:
Example: