domains

PUT `/v1/domains/{domainId}/email-routing/rules/{ruleId}`

Change a forwarding rule.

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 domains.dns.manage 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X PUT https://api.zinndigital.com/v1/domains/{domainId}/email-routing/rules/{ruleId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "matcher": <string>, "destinations": <string[]> }'

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

详细信息

Requires `domains.dns.manage`. The catch-all is a separate resource at the provider and cannot be changed through this path — use `PUT .../email-routing/catch-all`.

参数

名称	类型	必填	内容简介
`domainId (path)`	`Uuid`	是	The domain's id.
`ruleId (path)`	`string`	是	The provider's own id for the routing rule.

请求正文

名称	类型	必填	内容简介
`matcher`	`string`	是	—
`destinations`	`string[]`	是	—
`action`	`EmailRoutingAction`	否	`drop` is a chosen behaviour — it is how a catch-all silently discards spam — and is never inferred from an empty destination list.
`name`	`string`	否	—
`enabled`	`boolean`	否	—

响应

名称	类型	必填	内容简介
`rule_id`	`string`	是	—
`matcher`	`string`	是	The address this rule applies to. Empty for the catch-all.
`destinations`	`string[]`	是	—
`action`	`EmailRoutingAction`	是	`drop` is a chosen behaviour — it is how a catch-all silently discards spam — and is never inferred from an empty destination list.
`name`	`string`	是	—
`enabled`	`boolean`	是	—
`catch_all`	`boolean`	是	—
`unsupported`	`boolean`	是	`true` when the provider's rule uses a shape this API cannot express — a Worker target, say. Such a rule is shown read-only rather than hidden: hiding it would make this screen…

此端点可能返回的错误

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/domains/{domainId}/email-routing/rules/{ruleId}