blacklist/post_emails
Tool: create
Add one or more full email addresses to the blacklist.
Returns per-email results (added or skipped). Emails whose domain is already domain-blacklisted are skipped — they remain blacklisted: true via domain inheritance (see blacklist/get_emails_check), and the skip includes a per-item reason field.
Blacklist first, delete second. When you are also removing the contact (prospect/delete_by_id), suppress here first — the entry outlives the prospect record, but deleting first loses the address, and this call can still fail.
Email format is validated up front — malformed entries are rejected with per-item errors before anything is added. Fix and resubmit them.
Scoped, not global. This adds to the blacklist of the scope the call targeted (the organization, or a workspace/clientspace when
arguments.workspaceId/clientspaceIdwas set) — see blacklist for the scope model. It does not suppress the email in any other scope; add it there too if needed.
Body
| field | type | req | constraints | description |
|---|---|---|---|---|
| emails | array | ✓ | Array of full email address strings to blacklist. |
Response
201 — Partial or full add result.
| field | type | description |
|---|---|---|
| added | integer | Number of emails newly added to the blacklist. |
| emails | array | Normalized valid emails from the request. |
| skippedEmailCount | integer | Emails skipped because already blacklisted. |
| results[] | array | Per-email result items. |
| results[].email | string | Normalized email address. |
| results[].added | boolean | True if newly added. |
| results[].reason | string | Reason skipped, when not added (e.g. domain-blocked). |
Errors: 400, 401, 406, 409, 415, 422, 429, 500 — shared schema: schemas/errors.
Invoke
Call create with name: "blacklist/post_emails".