PUT /accounts/{account_id}/email-security/settings/block_senders/{pattern_id}
Replaces an existing blocked sender pattern in full. Unlike PATCH, every field is taken from the request body, so optional fields that are omitted are reset rather than left untouched. Use this when managing blocked senders declaratively.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
pattern_id |
String | Yes | |
account_id |
String | Yes |
Account identifier tag. |
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 |
|---|---|---|---|
id |
String | No |
Blocked sender pattern identifier. |
pattern_type |
String | Yes |
Type of pattern matching.
Valid values:
|
last_modified |
String | No |
Deprecated, use |
modified_at |
String | No | |
created_at |
String | No | |
is_regex |
Boolean | Yes | |
pattern |
String | Yes |
The pattern value to match. The format depends on |
comments |
String | No |
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.