Apollo Sequences · Outreach

apollo-rest-api / Search for contacts

Endpoint essentials API key access: api/v1/contacts/search or Master API key OAuth scopes: contacts_search Credit usage: 0 credits — Learn more about API pricing and credits. Contacts are people saved in Apollo. Use the search for contacts endpoint to search for the contacts that have been added to your team's Apollo account. This endpoint only returns contacts in the search results. To search for people in the Apollo database, call the people API search endpoint. To protect Apollo's performance for all users, this endpoint has a display limit of 50,000 records (100 records per page, up to 500 pages). Add more filters to narrow your search results as much as possible. Every field is an optional filter.

Private Gateway connection

Data below comes from the configured private Gateway. Provider activation remains governed by its evidence and policy gates.

unverifiedRequest shape unavailableUnverified

Published API evidence

Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

contact_label_ids body · optional
The Apollo IDs for the labels that you want to include in your search results. If you add multiple labels, Apollo will include all contacts connected to any of the labels, along with the other parameters, in the search results. Example: `['6095a710bd01d100a506d4ae']`
contact_stage_ids body · optional
The Apollo IDs for the contact stages that you want to include in your search results. If you add multiple contact stages, Apollo will include all contacts that match any of the stages, along with the other parameters, in the search results. Call the [list contact stages endpoint](https://docs.apollo.io/reference/list-contact-stages) to retrieve a list of all the contact stage IDs available in your Apollo account. Example: `6095a710bd01d100a506d4ae`
page body · optional
The page number of the Apollo data that you want to retrieve. Use this parameter in combination with the `per_page` parameter to make search results navigable and improve the performance of the endpoint. Example: `4`
per_page body · optional
The number of search results that should be returned for each page. Limiting the number of results per page improves the endpoint's performance. Use the `page` parameter to search the different pages of data. Example: `10`
q_keywords body · optional
Add a keyword search string to narrow the contacts in your team's Apollo account. Keywords should be related to the same search concept and can include names, job titles, employers or company names, or email addresses. Examples: `matthew helm`; `CEO`; `Sumware Software`
sort_ascending body · optional
Set to `true` to sort the matching contacts in ascending order. This parameter must be used with `sort_by_field`. Otherwise, the sorting logic is not applied. Example: `true`
sort_by_field body · optional
Sort the matching contacts by 1 of the following options: - `contact_last_activity_date`: The most recent activity date recorded first. - `contact_email_last_opened_at`: The most recent email opened date first. - `contact_email_last_clicked_at`: The most recent email clicked first. - `contact_created_at`: The most recently created first. - `contact_updated_at`: The most recently updated first.

Provider docs How to run it