PATCH
/
cloud
/
v1
/
ddos
/
profiles
/
{project_id}
/
{region_id}
/
{profile_id}
Update DDoS protection profile
curl --request PATCH \
  --url https://api.gcore.com/cloud/v1/ddos/profiles/{project_id}/{region_id}/{profile_id} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "fields": [
    {
      "base_field": 10,
      "field_value": [
        45046,
        45047
      ]
    }
  ],
  "ip_address": "11.111.111.1",
  "profile_template": 123
}'
{
  "tasks": [
    "d478ae29-dedc-4869-82f0-96104425f565"
  ]
}

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Path Parameters

​
project_id
integer
required

Unique identifier of the cloud project that owns the DDoS protection resources

Examples:

1

​
region_id
integer
required

Unique identifier of the cloud region where DDoS protection operations will be performed

Examples:

1

​
profile_id
integer
required

Unique identifier of the specific DDoS protection profile to be operated on

Examples:

1

Body

application/json
​
ip_address
required

IP address that will be protected by the DDoS protection profile

Examples:

"11.111.111.1"

​
profile_template
integer
required

Unique identifier of the DDoS protection template to use for this profile

Examples:

123

​
fields
CreateClientProfileFieldSerializer · object[]

List of field configurations that customize the protection parameters for this profile

Examples:
[
  {
    "base_field": 10,
    "field_value": [45046, 45047]
  }
]

Response

200 - application/json

OK

​
tasks
string[]
required

List of task IDs representing asynchronous operations. Use these IDs to monitor operation progress: * GET /v1/tasks/{task_id} - Check individual task status and details Poll task status until completion (FINISHED/ERROR) before proceeding with dependent operations.

Examples:
["d478ae29-dedc-4869-82f0-96104425f565"]