Search for Outreach Emails

Find emails based on their current status, such as whether they were delivered or opened. You can add multiple statuses. <br><br>Possible values include: <ul> <li> delivered </li> <li> scheduled </li> <li> drafted </li> <li> not_opened </li> <li> opened </li> <li> clicked </li> <li> unsubscribed </li> <li> demoed </li> <li> bounced </li> <li> spam_blocked </li> <li> failed_other </li> </ul>

Find emails based on the response sentiment of the recipient. This can include the recipient expressing interest in meeting or having a follow-up question. You can add multiple values.<br><br>Possible values include: <ul> <li> willing_to_meet </li> <li> follow_up_question </li> <li> person_referral </li> <li> out_of_office </li> <li> already_left_company_or_not_right_person </li> <li> not_interested </li> <li> unsubscribe </li> <li> none_of_the_above </li> </ul>

Find emails sent by specific users in your team's Apollo account. You can add multiple users. <br><br>Use the <a href="https://docs.apollo.io/reference/get-a-list-of-users" target="_blank">Get a List of Users endpoint</a> to retrieve IDs for all of the users within your Apollo account. <br><br>Example: 66302798d03b9601c7934ebf

Search for emails that are included in specific sequences in your Apollo account. You can search multiple sequences. Any sequence not included in this parameter will be exclude from search results.<br><br>To find sequence IDs, call the <a href="https://docs.apollo.io/reference/search-for-sequences" target="_blank">Search for Sequences endpoint</a> and identify the id value for the sequence. <br><br>Example: 66e9e215ece19801b219997f

Exclude emails from specific sequences in your Apollo account. You can exclude multiple sequences. Any sequence not excluded using this parameter will be included in search results.<br><br>To find sequence IDs, call the <a href="https://docs.apollo.io/reference/search-for-sequences" target="_blank">Search for Sequences endpoint</a> and identify the id value for the sequence. <br><br>Example: 66e9e215ece19801b219997f

Use this parameter in combination with the emailer_message_date_range[max] and emailer_message_date_range[min] parameters. Find emails based on 1 of the following options: <ul> <li> due_at: When emails are scheduled to be delivered. </li> <li> completed_at: When emails were delivered. </li> </ul>

Set the upper bound of the date range you want to search. <br><br>Use this parameter in combination with the emailer_message_date_range[min] and emailer_message_date_range_mode parameters. This date should fall after the emailer_message_date_range[min] date. <br><br>The date should be formatted as YYYY-MM-DD. <br><br>Example: 2025-10-30

Set the lower bound of the date range you want to search. <br><br>Use this parameter in combination with the emailer_message_date_range[max] and emailer_message_date_range_mode parameters. This date should fall before the emailer_message_date_range[max] date. <br><br>The date should be formatted as YYYY-MM-DD. <br><br>Example: 2025-10-30

Find emails based on the reason they were not sent. You can add multiple values.<br><br>Possible values include: <ul> <li> contact_stage_safeguard </li> <li> same_account_reply </li> <li> account_stage_safeguard </li> <li> email_unverified </li> <li> snippets_missing </li> <li> personalized_opener_missing </li> <li> thread_reply_original_email_missing </li> <li> no_active_email_account </li> <li> email_format_invalid </li> <li> ownership_permission </li> <li> email_service_provider_delivery_failure </li> <li> sendgrid_dropped_email </li> <li> mailgun_dropped_email </li> <li> gdpr_compliance </li> <li> not_valid_hard_bounce_detected <li> other_safeguard </li> <li> new_job_change_detected </li> <li> email_on_global_bounce_list </li> </ul>

Add keywords to narrow the search of the emails in your team's Apollo account. <br><br>Keywords should directly match at least part of an email's content. For example, searching the keyword James might return emails that were sent by James Smith. <br><br>Example: Jane

The page number of the Apollo data that you want to retrieve. <br><br>Use this parameter in combination with the per_page parameter to make search results for navigable and improve the performance of the endpoint. <br><br>Example: 4

The number of search results that should be returned for each page. Limiting the number of results per page improves the endpoint's performance. <br><br>Use the page parameter to search the different pages of data. <br><br>Example: 10