View Account Activity

Introducing Activity Search

The /activity/search endpoint allows you to search email events from your account’s “Reports > Activity” page matching the criteria in your request.

Accounts on the free plan can search up to 5 days of event history and paid plans up to 30 days by default. If paid plans utilize the Activity Duration feature to extend the storage (from 60 days up to 2 years) then event history will be available for the selected timeframe.

The request can return up to a maximum of 1,000 events by default and if the response exceeds that, a continue_token will be provided to retrieve the remaining results.


The /activity/search endpoint accepts 14 parameters with all listed below.

start_datedateISO-8601 formatted datetime which defaults to the current date at midnight. The range will be inclusive of start_date and exclusive of end_date. The timezone is UTC.
end_datedateISO-8601 formatted datetime which defaults to now. The timezone is UTC.
searchstringIf passed, will return all activities for emails containing this string in the Email_id, Subject, To, Recipient or BCC fields. To return activities with one or more text values, separate the text with '|' (e.g. 'text1 | text2').
search_subjectstringIf passed, will return all activities for emails containing this string in the email subject.
search_senderstringIf passed, will return all activities for emails containing this string in the email sender.
search_recipientstringIf passed, will return all activities for emails containing this string in the email recipient.
search_usernamesArray of stringsIf passed, will return all activities for emails sent by this/these username/s.
subaccountsArray of stringsIf passed, will return all activities for emails sent by this/these subaccount/s.
limitint32The maximum number of activities to return (Max: 100).
continue_tokenstringIf passed, will continue the search beyond the current page, using the same search parameters.
only_latestbooleanIf true, will only return the most recent event for each email returned. Default: false.
event_typesarray of stringsIf passed, will limit the returned activities to the provided event types.
Values: 'processed', 'soft-bounced', 'hard-bounced', 'rejected', 'spam', 'delivered', 'unsubscribed', 'resubscribed', 'opened' and 'clicked.'
include_headersbooleanReturn the full email headers with the response.
custom_hedersarray of stringsA list of header keys to parse out of the raw headers.

A search for bounced emails

In this search, we'll only make use of a few parameters covered above. However, you can combine many parameters to refine your search so it returns the particular data you need.

The search in this example will return soft and hard bounces encountered by a specific sending address within a defined period. To achieve this, the parameters used include the start_date, end_date, search_sender, event_types and limit (simply to limit the results to 1 for display purposes).

The example uses cURL. A range of languages are available which you can test and generate examples for on the “Search Activity” page of the API Reference section.

In the request headers, we POST to the “” endpoint, define the content type of “application/json” and include a valid API Key for authentication. The search parameters are set in the request body as JSON objects.

The Request

curl --request POST \
     --url \
     --header 'Content-Type: application/json' \
     --header 'X-Smtp2go-Api-Key: api-xxxxxxxxxxxx' \
     --header 'accept: application/json' \
     --data '
  "start_date": "2024-02-11",
  "end_date": "2024-02-13",
  "event_types": [
  "search_sender": "[email protected]",
  "limit: 1


A 200 response indicates a successful request and it would look similar to:

"request_id": "82aff18a-ca05-11ee-8a81-f23c9216ce11","data": {
  "events": [
      "from": "[email protected]",
      "recipient": "[email protected]",
      "subaccount_name": "Master account",
      "email_id": "1rZPGW-u6wXBO-2m",
      "date": "2024-02-12T05:54:07Z",
      "event": "hard-bounced",
      "subject": "Test bounce",
      "username": "TestUser",
       "sender": "[email protected]",
       "sender_full": "[email protected]",
       "to": "[email protected]",
      "smtp_response": "550-5.1.1 The email account that you tried to reach does not exist. Please try\\n550-5.1.1 double-checking the recipient's email address for typos or\\n550-5.1.1 unnecessary spaces. For more information, go to\\n550 5.1.1 n13-20020a05622a040d00b0042bf4b5caf6si7967427qtx.480 - gsmtp",
      "host": "",
      "outbound_ip": "",
      "byte_size": 1068
  "total_events": 3,
  "continue_token": "eyJhbGciO***********"

Note: a continue_token was included in the response as the search returned three results ("total_events": 3) but a limit of 1 was set in the request so it would only show one result for display purposes. The continue_token indicates the results exceed the limit (either passed in the request or the default value). In the event that you receive a continue_token string, you can pass it along with all of the original request data to continue the search and retrieve the next batch of results.

A 400 response indicates a failure. The response will include an error code and details covering what caused the error, similar to the below example where an incorrect event type was set:

  "request_id": "ce3fc5b4-ca08-11ee-bd82-f23c93560c0e",
  "data": {
    "error": "An error occurred processing the json data you sent with the request. Please make sure the data conforms to the specification for this call (see the documentation here: and try again. Don't forget to set Content-Type to 'application/json'.",
    "error_code": "E_ApiResponseCodes.NON_VALIDATING_IN_PAYLOAD",
    "field_validation_errors": {
      "fieldname": "event_types",
      "message": "The field 'event_types' was expecting a value from the allowed list ['processed', 'soft-bounced', 'hard-bounced', 'rejected', 'spam', 'delivered', 'unsubscribed', 'resubscribed', 'opened', 'clicked'] but instead found '['example']', Please correct your JSON payload and try again."

The activity/search endpoint can be used for simple requests such as the above or dive into more complex searches utilizing a range of parameters.

If you encounter an error when making a request, please submit a support ticket and provide the request_id in the response along with your request code as these will help our team investigate.