POST /zones/{zone_id}/email/routing/rules
Rules consist of a set of criteria for matching emails (such as an email being sent to a specific custom email address) plus a set of actions to take on the email (like forwarding it to a specific destination address).
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
zone_id |
String | Yes |
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 |
|---|---|---|---|
priority |
Number | No |
Priority of the routing rule. Default value: 0 |
actions[] |
Array | Yes |
List actions patterns. |
actions[].type |
String | Yes |
Type of supported action. Possible values:
|
actions[].value[] |
Array | No | |
name |
String | No |
Routing rule name. |
matchers[] |
Array | Yes |
Matching patterns to forward to your actions. |
matchers[].field |
String | No |
Field for type matcher. Possible values:
|
matchers[].type |
String | Yes |
Type of matcher. Possible values:
|
matchers[].value |
String | No |
Value for matcher. |
enabled |
Boolean | No |
Routing rule status. Possible values:
Default value: true |
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.