Search for Sequences

Endpoint essentials
API key accessapi/v1/emailer_campaigns/search or Master API key
OAuth scopesemailer_campaigns_search
Credit usage0 credits
Learn more about API pricing and credits.

Sequences are outreach campaigns that sales teams use to reach out to contacts over a planned period of time.

Use the Search for Sequences endpoint to search for the sequences that have been created for your team's Apollo account.

Each sequence in the response includes a sharing_permission object that describes who can access it. This object replaced the legacy permissions field, which is no longer returned by any sequence endpoint. Read sharing_permission as follows, for team members who don't hold a permission profile that grants access to every sequence in the workspace:

Sequence accessValues returned
Only the owner, plus anyone listed in sharing_accessesvisibility: restricted, access_type: null
The whole team can view the sequencevisibility: everyone, access_type: can_view
The whole team can use and edit the sequencevisibility: everyone, access_type: can_edit or full_access

The owner_id field matches the sequence's user_id, and is_owner tells you whether the authenticated user owns the sequence.

Permission profiles can widen this. A team member whose profile lets them view and edit all sequences can access a restricted sequence they don't own and that was never explicitly shared with them, so treat the table above as the baseline rather than a hard boundary.

To change a sequence's sharing, call the Update a Sequence endpoint with the sharing_permission object.

Query Params
string

Add keywords to narrow the search of the sequences in your team's Apollo account.

Keywords should directly match at least part of a sequence's name. For example, searching the keyword marketing might return the result NY Marketing Sequence, but not NY Marketer Conference 2025 attendees.

This parameter only searches sequence names, not other sequence fields.

Example: marketing conference attendees

string

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 for navigable and improve the performance of the endpoint.

Example: 4

string

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

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/plain