API Reference
See the full request/response schema and parameters in the API Reference.
Core concepts
Recommended flow
Simple filters
Top-level shape
Supported operators
The capabilities response exposes supported simple-query operators insimple_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.
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_filtersoperators such as$ne,$nin,$not, and$norto exclude records that match field conditions. - Use the top-level exclusion fields,
exclude_entity_idsorexclude_list_ids, to suppress specific people or companies by ID. See Search Exclusions for identifier formats, saved lists, and limits.
page_size.
Query examples
Find a company by website domain:$search:
$elemMatch on the inner nested path:
DSL filters
Top-level shape
Supported query clauses
Query examples
Range filter:must_not:
Filter capabilities
simple_filters operators and DSL limits.
Query parameters
Example request
Response shape
Limits
Field entry
Each item infields 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
Scoped query
A scope takes nofilters.sort, filters.size, simple_filters.$sort, or simple_filters.$limit.
Example request
Global:Response fields
Nested fields
For nested fields such astechnologies_used.technology, counts are record counts, and each filter_snippet is wrapped in a nested clause, ready to use in filters.
Search query
Request
Request flow
- First request: send exactly one of
simple_filters,filters,query,parsed_query, orsearch_id, plus any options above. - Next page: send only
{"cursor": "..."}. Mode, page size, output shape, and exclusions carry over.
Effective result cap
The smallest ofmax_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_entity_ids:
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.Related
For new integrations, see Filter Search.