Menu

Expand
Rate this page:

Bounces API

An email is considered bounced when the message is undeliverable and then returned to the server that sent it. Bounced emails can be either permanent or temporary failures to deliver the message.

For more information, see our Bounces documentation.

You can also manage bounced emails from the Suppression settings menu in the Twilio SendGrid App.

Retrieve all bounces

GET /v3/suppression/bounces

Base url: https://api.sendgrid.com

This endpoint allows you to retrieve a paginated list of all your bounces.

You can use the limit query parameter to set the page size. If your list contains more items than the page size permits, you can make multiple requests. Use the offset query parameter to control the position in the list from which to start retrieving additional items.

Authentication

  • API Key

Headers

Authorization
string
default: Bearer <<YOUR_API_KEY_HERE>>
required
Accept
string
default: application/json
required
on-behalf-of
string

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.

default: None

Query String

start_time
integer

Refers start of the time range in unix timestamp when a bounce was created (inclusive).

default: None
end_time
integer

Refers end of the time range in unix timestamp when a bounce was created (inclusive).

default: None
limit
integer

limit sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.

default: None
offset
integer

The number of items in the list to skip over before starting to retrieve the items for the requested page. The default offset of 0 represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the offset to the page size as determined by limit. Use multiples of the page size as your offset to request further consecutive pages. E.g. assume your page size is set to 10. An offset of 10 requests the second page, an offset of 20 requests the third page and so on, provided there are sufficiently many items in your list.

default: 0
email
string

Specifies which records to return based on the records' associated email addresses. For example, sales returns records with email addresses that start with 'sales', such as salesdepartment@example.com or sales@example.com. You can also use %25 as a wildcard. For example, %25market returns records containing email addresses with the string 'market' anywhere in the email address, and %25market%25tree returns records containing email addresses with the string 'market' followed by the string 'tree'. Any reserved characters should be percent-encoded, e.g., the @ symbol should be encoded as %40.

default: None

Responses

array[object]
created
number

The unix timestamp for when the bounce record was created at SendGrid.

email
string

The email address that was added to the bounce list.

format: email
reason
string

The reason for the bounce. This typically will be a bounce code, an enhanced code, and a description.

status
string

Enhanced SMTP bounce response

object
errors
array[object]
message
string

the error message

required
field
string or null

the field that generated the error

help
object

helper text or docs for troubleshooting

id
string
{
  "errors": [
    {
      "field": "field_name",
      "message": "error message"
    }
  ]
}

Retrieving paginated results

To perform a request for the first page of the paginated list of all bounces using the default page size, you can omit the limit and offset query parameters:

Loading Code Sample...
        
        

        Retrieve first page from list of all bounces

        If you want to specify a page size of your choice, you can use the limit query parameter. Assume you want a page size of no more than 5 items per request, to retrieve the first page you can use the limit parameter without specifying an offset:

        Loading Code Sample...
              
              
              Setting page size to 5 using the limit query parameter

              Retrieve first page from list of all bounces with a specified page size

              Setting page size to 5 using the limit query parameter

              If you want to retrieve items beyond the first page, you can use the offset parameter as follows. Assume you are still working with a page size of 5 as determined by your limit query parameter and you have more than 15 items. To request the fourth page of items, you can use the offset parameter to skip over the first 15 items, i.e. you start retrieving items starting after the first three pages of 5 items each:

              Loading Code Sample...
                    
                    
                    Using the offset query parameter in combination with the limit query parameter

                    Retrieve a specific page from the list of all bounces

                    Using the offset query parameter in combination with the limit query parameter

                    Use the email query parameter to filter results

                    The code samples below show how to use the email query parameter to filter the Bounce records returned by the GET request. A Bounce record is included in the results if the Bounce's email property starts with the the value of the email query parameter. One or more %25 wildcards can be used in the email query parameter.

                    Any reserved characters should be percent-encoded to avoid any unintended encoding/decoding of characters.

                    Filter results without wildcard

                    The code sample below shows examples of how to GET all Bounce records with email properties that begin with the string "sales".

                    Loading Code Sample...
                          
                          
                          GET all Bounce records with email properties that start with "sales"

                          Filter results without wildcard

                          GET all Bounce records with email properties that start with "sales"

                          This request would return Bounces with email addresses that start with "sales", such as salesteam@example.com or sales@example.com.

                          Filter results with wildcard

                          The code sample below shows examples of how to GET all Bounce records with email properties that contain the string "sales" anywhere in the email address.

                          Loading Code Sample...
                                
                                
                                GET all Bounce records with email properties that contain the string "sales" anywhere in the email address

                                Filter results with a wildcard

                                GET all Bounce records with email properties that contain the string "sales" anywhere in the email address

                                This request would return Bounces with email addresses that contain "sales" anywhere in the email address, such as george@sales.example.com or sales@example.com.

                                Rate this page:

                                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.

                                Loading Code Sample...
                                      
                                      
                                      

                                      Thank you for your feedback!

                                      Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

                                      Sending your feedback...
                                      🎉 Thank you for your feedback!
                                      Something went wrong. Please try again.

                                      Thanks for your feedback!

                                      thanks-feedback-gif