Blocks happen when your email is rejected because of an issue with the message itself rather than an issue with the recipient's address.
There are several causes for blocked emails. For example, your mail server IP address may be blocked by an ISP, or the receiving server may flag the message content using a filter. Twilio SendGrid will not suppress future messages to blocked addresses by default.
For more information, please see our Blocks documentation.
You can also see your Blocks in the Suppressions settings menu of the Twilio SendGrid App.
This endpoint allows you to delete all email addresses on your blocks list.
There are two options for deleting blocked emails:
delete_all
to true
in the request body.emails
array of the request body.Bearer <<YOUR_API_KEY_HERE>>
The on-behalf-of
header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>
). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>
). See On Behalf Of for more information.
application/json
Indicates if you want to delete all blocked email addresses.
The specific blocked email addresses that you want to delete.
No properties defined
1const client = require("@sendgrid/client");2client.setApiKey(process.env.SENDGRID_API_KEY);34const data = {5delete_all: false,6emails: ["example1@example.com", "example2@example.com"],7};89const request = {10url: `/v3/suppression/blocks`,11method: "DELETE",12body: data,13};1415client16.request(request)17.then(([response, body]) => {18console.log(response.statusCode);19console.log(response.body);20})21.catch((error) => {22console.error(error);23});