Skip to main content

API Reference

See the full request/response schema and parameters in the API Reference.
POST /search/start-filter-search is deprecated and returns a Deprecation header. Use POST /search/query, which takes the same filters and returns the same response.

Core concepts

Simple filters

Top-level shape

Supported operators

The capabilities response exposes supported simple-query operators in simple_query_operators.

Nested array matching

$elemMatch queries fields inside nested arrays. It is keyed on the field’s nested_path from capabilities, which is not always the outermost array: currentCompanies.company.companyId has nested_path: "currentCompanies", and currentCompanies.positions.title has nested_path: "currentCompanies.positions", so $elemMatch on currentCompanies cannot reference a positions field.
Inside $elemMatch, use the field’s full dotted path. A relative path with a dot, such as company.companyId, returns a 400, although its message suggests a relative path.
In people mode, conditions inside one $elemMatch on currentCompanies, previousCompanies, educations, or a positions path hold on the same entry. On any other path, each condition can match a different entry. Find people currently at a specific company by numeric LinkedIn company ID, which company results expose as source_id:

Excluding results

There are two ways to exclude records:
  • Use simple_filters operators such as $ne, $nin, $not, and $nor to exclude records that match field conditions.
  • Use the top-level exclusion fields, exclude_entity_ids or exclude_list_ids, to suppress specific people or companies by ID. See Search Exclusions for identifier formats, saved lists, and limits.
ID-based exclusions apply after matching, so a page can hold fewer rows than page_size.

Query examples

Find a company by website domain:
Exclude companies in specific industries:
Exclude records that match any disallowed condition:
Find US-based companies sorted by employee count descending, capped to 8 total results:
Find Canadian companies that have raised any amount and mention technology in categories or keywords:
Search several fields at once with $search:
Find people by current job title:
Fields with a doubly nested path accept $elemMatch on the inner nested path:

DSL filters

Top-level shape

Supported query clauses

Query examples

Range filter:
Multi-field full-text search:
Nested query:
Exclude with must_not:

Filter capabilities

Returns every field you can query, sort, range, or get top values for, plus the simple_filters operators and DSL limits.
Call this first to discover what is filterable. Only fields in fields, and their .keyword and .raw forms, can be queried.

Query parameters

Example request

Response shape

Limits

Field entry

Each item in fields describes one queryable field. To list fields by property, filter the capabilities response, for example with jq '.fields[] | select(.supports_top_values) | .field'.

Example response

Trimmed to two representative fields, a top-level keyword and a nested numeric.

Field values

Returns the most common values of one field, ranked by record count, optionally scoped by a query.

Scoped query

A scope takes no filters.sort, filters.size, simple_filters.$sort, or simple_filters.$limit.
A high top_k lists the valid values of an enum-like field before filtering.

Example request

Global:
Scoped:

Response fields

Nested fields

For nested fields such as technologies_used.technology, counts are record counts, and each filter_snippet is wrapped in a nested clause, ready to use in filters.

Search query

Runs a paginated search and returns the first page.

Request

Request flow

  1. First request: send exactly one of simple_filters, filters, query, parsed_query, or search_id, plus any options above.
  2. Next page: send only {"cursor": "..."}. Mode, page size, output shape, and exclusions carry over.
See Paginate with cursors for every cursor rule.

Effective result cap

The smallest of max_results, simple_filters.$limit, and filters.size applies. The response reports it as max_results, with remaining_results left after each page.

Response fields

For every response field, see Search Results → Query response.

Example request

Fresh search:
Exclude specific people with exclude_entity_ids:
For identifier formats, saved lists, and limits, see Search Exclusions. Re-run a previous search:
Next page:

Photo and logo URLs

People rows carry image URLs that need no credentials, so they can be embedded directly in an <img> tag, CRM record, or spreadsheet cell. When logoUrl holds a bare 32-character key instead of a URL, the photo is at https://api.sixtyfour.ai/v1/media/profiles/{key}. These URLs do not expire. See Rate Limits and Handling Errors.

Export search results

Export results from any search as a CSV. See Export Search Results for the full endpoint reference.

Example usage

The following examples walk through the full recommended flow: discover valid fields, inspect top values for one field, then paginate through results.

Rate limits

For per-endpoint limits, see Rate Limits.

Pricing

See Credit Costs for more information.
For new integrations, see Filter Search.