client.suppressions
كل دالّة في مساحة الأسماء هذه: توقيعها ومعلماتها وما تُرجعه ومثال عليها.
الدوالّ
The addresses this workspace will not send to: hard bounces, complaints and the ones you block by hand.
suppressions.list
List one page of the suppression list
list(q: nil, reason: nil, limit: nil, cursor: nil, api_key: nil) -> OpenEmail::PageReturns one page of the addresses this workspace will not send to, newest first: every address that bounced hard, complained, or was added by hand. list_all collects every page and iterate walks them lazily.
A send to a suppressed address is refused for that recipient before anything leaves, and a message whose recipients are all suppressed fails outright. The list belongs to the whole workspace, so a key limited to some addresses reads all of it, and a row names the recipient, never which of your addresses sent to it.
removable says whether remove will take the address off. A hard bounce is permanent here, because the address could not take mail. A complaint or a manual entry can be removed.
المعلمات
qStringSearches the address, the reason and the detail. Words match loosely, and a close spelling is tried when nothing matches exactly.
reasonStringKeeps one kind:
bounce,complaintormanual.limitIntegerPage size, from 1 to 100. The server defaults to 25.
cursorStringThe
next_cursorof the previous page. Leave it out for the first page.api_keyStringOverrides the client API key for this call only.
يُرجع
An OpenEmail::Page of Hashes, with items, has_more? and next_cursor. Each item has id, email, reason, detail, removable and createdAt.
مثال
page = client.suppressions.list(reason: "complaint") p page.items.map { |row| [row[:email], row[:createdAt]] }ملاحظات
Needs
settings:read, the scope the Blocked addresses screen in Settings is gated on.The cursor is opaque and holds where the last row sat, so an address removed between pages never breaks the walk. A cursor this list did not hand out is a 400
invalid_cursor.
متاح أيضًا في
- API
GET /suppressions- TypeScript
suppressions.list()- Python
suppressions.list()- CLI
openemail suppressions list
suppressions.list_all
Collect the whole suppression list into one array
list_all(q: nil, reason: nil, limit: nil, cursor: nil, api_key: nil) -> Array<Hash>Walks every page of list and returns every suppressed address in one Array, newest first. One request per page, with the same filters on each.
المعلمات
qStringSearches the address, the reason and the detail. Words match loosely, and a close spelling is tried when nothing matches exactly.
reasonStringKeeps one kind:
bounce,complaintormanual.limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
يُرجع
An Array of Hashes holding every suppressed address, each with the fields list returns.
مثال
all = client.suppressions.list_all(limit: 100) blocked = all.map { |row| row[:email] }.to_set puts blocked.include?("[email protected]")ملاحظات
If any page fails, the error is raised and the rows already fetched are discarded.
متاح أيضًا في
- API
GET /suppressions- TypeScript
suppressions.listAll()- Python
suppressions.list_all()
suppressions.iterate
Stream the suppression list one address at a time
iterate(q: nil, reason: nil, limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>Returns an Enumerator that yields one suppressed address at a time, newest first, and requests the next page only once the current one is drained. Nothing is fetched until you consume it, and breaking out of the loop stops the requests. Given a block, it yields each row to the block instead.
المعلمات
qStringSearches the address, the reason and the detail. Words match loosely, and a close spelling is tried when nothing matches exactly.
reasonStringKeeps one kind:
bounce,complaintormanual.limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
يُرجع
An Enumerator of Hashes, one suppressed address per step (or yields each one to a block).
مثال
client.suppressions.iterate(q: "example.com") do |row| puts "#{row[:email]} #{row[:reason]}"endملاحظات
Pages are fetched only as they are needed, so an abandoned loop costs only the pages you consumed.
متاح أيضًا في
- API
GET /suppressions- TypeScript
suppressions.iterate()- Python
suppressions.iterate()
suppressions.get
Read one suppressed address by id
get(id, api_key: nil) -> HashReturns one row of the suppression list: the address, why it is there, the detail the bounce or complaint carried, whether it can be removed and when it was added.
المعلمات
idStringمطلوبThe id from
list.api_keyStringOverrides the client API key for this call only.
يُرجع
A Hash with id, email, reason, detail, removable and createdAt.
مثال
row = client.suppressions.get("7b1e2c3d-4f5a-4b6c-8d7e-9f0a1b2c3d4e") puts row[:email], row[:removable]ملاحظات
An id that is not on this workspace is a 404
resource_not_found.
متاح أيضًا في
- API
GET /suppressions/{id}- TypeScript
suppressions.get()- Python
suppressions.get()- CLI
openemail suppressions get
suppressions.add
Stop sending to an address
add(body = nil, api_key: nil, **fields) -> HashPuts an address on the suppression list by hand, with reason: "manual", so no address in the workspace sends to it again until it is removed. It is the Block an address control on the Blocked addresses screen.
Adding an address that is already there changes nothing: the server answers 200 with the row it already holds, whatever its reason, where a new entry answers 201. Either way you get the row back. A new entry fires suppression.added to the webhooks that asked for it.
المعلمات
emailStringمطلوبThe address to stop sending to. It is trimmed and lower cased.
api_keyStringOverrides the client API key for this call only.
يُرجع
A Hash for the address, new or already there, with the fields get returns.
مثال
row = client.suppressions.add(email: "[email protected]") puts row[:reason], row[:createdAt]ملاحظات
Safe to repeat: a second add finds the first entry, so the SDK retries it after a network failure.
A key limited to particular addresses or domains is refused with 422
capability_unsupported, because the list stops mail from every address in the workspace. So is an app connected by anybody but the owner.
متاح أيضًا في
- API
POST /suppressions- TypeScript
suppressions.add()- Python
suppressions.add()- CLI
openemail suppressions add
suppressions.remove
Allow mail to an address again
remove(id, api_key: nil) -> HashTakes an address off the suppression list, so mail may go to it again. It is Allow again on the Blocked addresses screen, and it fires suppression.removed.
Only a complaint or a manual entry can be removed. A hard bounce answers 409 suppression_not_removable and stays, because the address could not take mail: check it is spelled right and send to the corrected one instead.
المعلمات
idStringمطلوبThe id from
list.api_keyStringOverrides the client API key for this call only.
يُرجع
A Hash with object set to suppression, the id, the email, and deleted set to true.
مثال
row = client.suppressions.list(q: "[email protected]").items.first begin client.suppressions.remove(row[:id]) if rowrescue OpenEmail::ConflictError puts "#{row[:email]} bounced hard, so it stays on the list"endملاحظات
The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked.
A key limited to particular addresses or domains is refused with 422
capability_unsupported.