Blocks API
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.
Retrieve a specific block
GET /v3/suppression/blocks/{email}
Base url: https://api.sendgrid.com
This endpoint allows you to retrieve a specific email address from your blocks list.
Authentication
- API Key
Headers
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.
Path Parameters
The email address of the specific block.
default: NoneResponses
A Unix timestamp indicating when the email address was added to the blocks list.
The email address that was added to the block list.
format: emailAn explanation for the reason of the block.
The status of the block.
[
{
"created": 1443651154,
"email": "example@example.com",
"reason": "error dialing remote address: dial tcp 10.57.152.165:25: no route to host",
"status": "4.0.0"
}
]Need some help?
We all do sometimes. Get help now from the Twilio SendGrid Support Team.
Running into a coding hurdle? Lean on the wisdom of the crowd by browsing the SendGrid tag on Stack Overflow or visiting Twilio's Stack Overflow Collective.
