> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/employee-data/api/search-filters.md).

# Search Filters: Employee API

Filter Coresignal multi-source employee data using named request-body parameters.

{% columns %}
{% column width="16.666666666666664%" %}
Data type:

Query type:

URLs:
{% endcolumn %}

{% column %}
Employee data

Coresignal's custom filters

<https://api.coresignal.com/cdapi/v2/employee\\_multi\\_source/search/filter>
{% endcolumn %}
{% endcolumns %}

***

The Employee API offers structured endpoints for filtering multi-source employee data with parameters. Instead of building custom Elasticsearch DSL queries, you can send standard, named key-value filters in the request body. Each filter parameter corresponds to the response field it filters.

## Universal operator rules

These evaluation rules apply across all parameters:

* Single value vs. list:
  * Providing a single value evaluates as an exact match (`equals`).
  * Providing an array/list of values evaluates as `any of` (logical `OR` within that field).
* Cross-parameter combination:
  * Multiple parameters are combined using `AND` logic.
  * Cross-field `OR` is not supported. If your query requires logical `OR` across different fields, use standard Elasticsearch DSL endpoints instead.
* Exclusions (`exclude_`):
  * Any parameter prefixed with `exclude_` acts as a negative match (`NOT`).
* Null values:
  * Passing an explicit `null` targets records that contain no value for that specific field.
  * Explicit `null` values are not permitted on `exclude_` parameters.
* Error handling and unknown parameters:
  * Any unrecognized or invalid parameter name will trigger a `422` error that explicitly names the offending parameter.

### Free-text search operators

Free-text fields (like `keyword`, `summary`, or `experience_description`) support symbol-based query operators:

| Operator | Action              | Example                          |
| -------- | ------------------- | -------------------------------- |
| `\|`     | Logical OR          | `Software \| Internet`           |
| `+`      | Logical AND         | `Python + Django`                |
| `-`      | Logical NOT         | `Cloud -AWS`                     |
| `""`     | Exact phrase match  | `"Artificial Intelligence"`      |
| `()`     | Precedence grouping | `(Fintech \| Payments) + Mobile` |

{% hint style="warning" %}

#### Important: syntax differences

Text words `OR`, `AND`, and `NOT` are not interpreted as operators in this API – they are treated as literal search terms. You must use the symbols `|`, `+`, and `-`.

A malformed free-text operator syntax does not raise an API error. It will result in fewer or zero matching records.
{% endhint %}

## Filter reference

The filters below are grouped into categories to help you find the right parameter faster.

### Personal and professional demographics

<table data-search="false"><thead><tr><th width="295.3984375">Parameter</th><th width="130.1953125">Type</th><th width="295.296875">Description</th></tr></thead><tbody><tr><td><code>full_name</code></td><td>String</td><td>Full name of the employee</td></tr><tr><td><code>headline</code></td><td>String</td><td>The professional headline or tagline. Supports symbol operators</td></tr><tr><td><code>summary</code></td><td>String</td><td>Personal bio/summary. Supports symbol operators</td></tr><tr><td><code>keyword</code></td><td>String</td><td>Broad keyword search. Targets the <code>summary</code>, <code>experience_description</code>, and <code>experience_position_title</code> fields. Supports symbol operators</td></tr><tr><td><code>inferred_skills</code></td><td>String</td><td>Derived or inferred professional skills</td></tr><tr><td><code>location_full</code></td><td>String</td><td>Full textual description of the employee's location</td></tr><tr><td><code>location_country</code></td><td>String</td><td>Name of the location country</td></tr><tr><td><code>location_country_iso2</code></td><td>String</td><td>2-letter ISO 3166-1 alpha-2 country code (e.g., <code>US</code>, <code>GB</code>)</td></tr><tr><td><code>location_city</code></td><td>String</td><td>Employee's resident city</td></tr><tr><td><code>is_working</code></td><td>Boolean</td><td>Flag indicating if the employee is currently employed (<code>true</code> / <code>false</code>)</td></tr><tr><td><code>is_decision_maker</code></td><td>Boolean</td><td>Flag identifying the employee as a decision-maker within their role (<code>true</code> / <code>false</code>)</td></tr><tr><td><code>professional_network_url</code></td><td>String</td><td>URL to their employee profile on supported professional networks</td></tr><tr><td><code>total_experience_duration_months_gte</code></td><td>Integer</td><td>Minimum total career length in months (<span class="math">\ge</span>)</td></tr><tr><td><code>total_experience_duration_months_lte</code></td><td>Integer</td><td>Maximum total career length in months (<span class="math">\le</span>)</td></tr><tr><td><code>projected_total_salary_median_gte</code></td><td>Integer</td><td>Median estimated total annual salary floor (<span class="math">\ge</span>)</td></tr><tr><td><code>projected_total_salary_median_lte</code></td><td>Integer</td><td>Median estimated total annual salary ceiling (<span class="math">\le</span>)</td></tr><tr><td><code>created_at_gte</code></td><td>String</td><td>Record creation date floor with day precision (<code>YYYY-MM-DD</code>)</td></tr><tr><td><code>created_at_lte</code></td><td>String</td><td>Record creation date ceiling with day precision (<code>YYYY-MM-DD</code>)</td></tr><tr><td><code>updated_at_gte</code></td><td>String</td><td>Record last updated date floor with day precision (<code>YYYY-MM-DD</code>)</td></tr><tr><td><code>updated_at_lte</code></td><td>String</td><td>Record last updated date ceiling with day precision (<code>YYYY-MM-DD</code>)</td></tr></tbody></table>

### Current employment

<table data-search="false"><thead><tr><th width="294.80859375">Parameter</th><th width="129.97265625">Type</th><th width="294.21875">Description</th></tr></thead><tbody><tr><td><code>active_experience</code></td><td>Boolean</td><td>Checks if the experience is active</td></tr><tr><td><code>active_experience_title</code></td><td>String</td><td>Position title of the active job role</td></tr><tr><td><code>active_experience_company_id</code></td><td>Integer</td><td>Unique internal ID of the currently employing company</td></tr><tr><td><code>active_experience_company_name</code></td><td>String</td><td>Name of the currently employing company</td></tr><tr><td><code>active_experience_company_industry</code></td><td>String</td><td>Industry classification of the active employer</td></tr><tr><td><code>active_experience_company_is_saas</code></td><td>Boolean</td><td>Flag indicating if current employer is a SaaS business (<code>true</code> or <code>false</code>)</td></tr><tr><td><code>active_experience_company_business_model</code></td><td>String</td><td>Business model of the current employer (e.g., <code>B2B</code>, <code>B2C</code>)</td></tr><tr><td><code>active_experience_company_business_areas</code></td><td>String</td><td>Operational/functional areas of the current employer</td></tr><tr><td><code>active_experience_management_level</code></td><td>String</td><td>Management tier (e.g., <code>Director</code>, <code>Manager</code>, <code>C-Level</code>)</td></tr><tr><td><code>active_experience_department</code></td><td>String</td><td>Employee's current functional department (e.g., <code>Sales</code>, <code>Engineering</code>)</td></tr></tbody></table>

### Experience information

These parameters check across the employee's full job history.

<table data-search="false"><thead><tr><th width="294.55078125">Parameter</th><th width="130.18359375">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>experience_position_title</code></td><td>String</td><td>Matching past or present title. Supports symbol operators</td></tr><tr><td><code>experience_description</code></td><td>String</td><td>Free-text on historical role descriptions. Supports symbol operators</td></tr><tr><td><code>experience_company_name</code></td><td>String</td><td>Matching past or present employer name</td></tr><tr><td><code>exact_experience_company_name</code></td><td>String</td><td>Exact matching past or present employer name</td></tr><tr><td><code>experience_company_website</code></td><td>String</td><td>Website domain of any past or present employer</td></tr><tr><td><code>exact_experience_company_website</code></td><td>String</td><td>Exact website URL of any past or present employer</td></tr><tr><td><code>experience_company_professional_network_url</code></td><td>String</td><td>Professional network page URL for any past or present employer</td></tr><tr><td><code>experience_company_industry</code></td><td>String</td><td>Industry sector of any past or present employer</td></tr><tr><td><code>experience_company_id</code></td><td>Integer</td><td>Internal ID of any past or present employer</td></tr><tr><td><code>experience_company_size_range</code></td><td>String</td><td>Standard employee size bracket of the past or present employer. Find all available <code>size_range</code> values on a general <a href="https://docs.coresignal.com/api-introduction/requests/search-filters.md#possible-input-values">Search Filter</a> page</td></tr><tr><td><code>experience_company_employees_count_gte</code></td><td>Integer</td><td>Minimum headcount of any past or present employer (<span class="math">\ge</span>)</td></tr><tr><td><code>experience_company_employees_count_lte</code></td><td>Integer</td><td>Maximum headcount of any past or present employer (<span class="math">\le</span>)</td></tr><tr><td><code>experience_date_from_gte</code></td><td>String</td><td>Earliest start date for any past or present role (<code>YYYY-MM-DD</code>)</td></tr><tr><td><code>experience_date_to_lte</code></td><td>String</td><td>Latest end date for any past or present role (<code>YYYY-MM-DD</code>)</td></tr></tbody></table>

### Education and certifications

<table data-search="false"><thead><tr><th width="294.703125">Parameter</th><th width="129.96484375">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>education_institution_name</code></td><td>String</td><td>Name of attended academic institutions</td></tr><tr><td><code>exact_education_institution_name</code></td><td>String</td><td>Case-insensitive match on the complete institution name</td></tr><tr><td><code>education_institution_url</code></td><td>String</td><td>Website or profile URL of the institution</td></tr><tr><td><code>education_degree</code></td><td>String</td><td>Academic degree earned (e.g., <code>Bachelor of Science</code>, <code>PhD</code>)</td></tr><tr><td><code>education_description</code></td><td>String</td><td>Detailed notes, major, or honors. Supports symbol operators</td></tr><tr><td><code>education_date_from_year_gte</code></td><td>Integer</td><td>Start year of education (<code>YYYY</code>)</td></tr><tr><td><code>education_date_to_year_lte</code></td><td>Integer</td><td>Graduation / end year of education (<code>YYYY</code>)</td></tr><tr><td><code>certifications_title</code></td><td>String</td><td>Professional credentials and certificates title</td></tr></tbody></table>

### Exclusion variants

Omit employees using `exclude_` fields:

<table data-search="false"><thead><tr><th width="294.69921875">Exclusion parameter</th><th width="129.8671875">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>exclude_active_experience_title</code></td><td>String</td><td>Exclude employees by active job title</td></tr><tr><td><code>exclude_active_experience_company_id</code></td><td>Integer</td><td>Exclude employees by current employer's ID</td></tr><tr><td><code>exclude_active_experience_company_name</code></td><td>String</td><td>Exclude employees by current employer's name</td></tr><tr><td><code>exclude_active_experience_company_industry</code></td><td>String</td><td>Exclude employees by current employer's industry</td></tr><tr><td><code>exclude_location_country_iso2</code></td><td>String</td><td>Exclude employees in specific countries</td></tr><tr><td><code>exclude_location_city</code></td><td>String</td><td>Exclude employees from specific cities</td></tr><tr><td><code>exclude_active_experience_management_level</code></td><td>String</td><td>Exclude employees by active management level</td></tr><tr><td><code>exclude_active_experience_department</code></td><td>String</td><td>Exclude employees by active department</td></tr><tr><td><code>exclude_headline</code></td><td>String</td><td>Exclude employees by professional headline terms. Supports symbol operators</td></tr><tr><td><code>exclude_inferred_skills</code></td><td>String</td><td>Exclude employees with specific skills</td></tr></tbody></table>

## Complete request schema

{% code lineNumbers="true" expandable="true" %}

```json
{
  "full_name": "string",
  "headline": "string",
  "summary": "string",
  "keyword": "string",
  "inferred_skills": "string",
  "professional_network_url": "string",
  "is_working": true,
  "is_decision_maker": true,
  "total_experience_duration_months_gte": 0,
  "total_experience_duration_months_lte": 0,
  "projected_total_salary_median_gte": 0,
  "projected_total_salary_median_lte": 0,
  "location_full": "string",
  "location_country": "string",
  "location_country_iso2": "DM",
  "location_city": "string",
  "active_experience_title": "string",
  "active_experience_management_level": "string",
  "active_experience_department": "string",
  "active_experience_company_id": 1,
  "active_experience_company_name": "string",
  "active_experience_company_industry": "string",
  "active_experience_company_is_saas": true,
  "active_experience_company_business_model": "string",
  "active_experience_company_business_areas": "string",
  "active_experience": true,
  "experience_position_title": "string",
  "experience_company_name": "string",
  "exact_experience_company_name": "string",
  "experience_company_website": "string",
  "exact_experience_company_website": "string",
  "experience_company_professional_network_url": "string",
  "experience_company_industry": "string",
  "experience_company_size_range": "string",
  "experience_company_id": 1,
  "experience_company_employees_count_gte": 0,
  "experience_company_employees_count_lte": 0,
  "experience_date_from_gte": "string",
  "experience_date_to_lte": "string",
  "experience_description": "string",
  "education_institution_name": "string",
  "exact_education_institution_name": "string",
  "education_institution_url": "string",
  "education_degree": "string",
  "education_description": "string",
  "education_date_from_year_gte": 1000,
  "education_date_to_year_lte": 1000,
  "certifications_title": "string",
  "created_at_gte": "string",
  "created_at_lte": "string",
  "updated_at_gte": "string",
  "updated_at_lte": "string",
  "exclude_headline": "string",
  "exclude_inferred_skills": "string",
  "exclude_location_country_iso2": "Zs",
  "exclude_location_city": "string",
  "exclude_active_experience_title": "string",
  "exclude_active_experience_management_level": "string",
  "exclude_active_experience_department": "string",
  "exclude_active_experience_company_id": 1,
  "exclude_active_experience_company_name": "string",
  "exclude_active_experience_company_industry": "string"
}
```

{% endcode %}

## Sample query

Fetch US-based employees with specific employers:

{% code title="Bash" %}

```json
curl -X 'POST' \
  'https://api.coresignal.com/cdapi/v2/employee_multi_source/search/filter' \
  -H 'accept: application/json' \
  -H 'apikey: {API_KEY}' \
  -H 'Content-Type: application/json' \
  -d '{
    "experience_company_name": ["Google", "Amazon"],
    "location_country": "United States"
}'
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/employee-data/api/search-filters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
