Feature Requests

Introduce list management endpoints (e.g., POST /lists, POST /lists/{id}/contacts) and support an exclude_list_ids parameter in the /person/search API to filter out known contacts without passing large arrays of individual IDs. This will reduce payload sizes, improve query performance, and simplifies the client-side integration

Using nested queries can help uncover which individuals are a particular job role at a company during a particular time range.

Enable Elasticsearch query options that are currently disabled due to resource requirements https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-fuzzy-query.html https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-minimum-should-match.html

I would like a natural language interface to create SQL queries based on the data available in your platform. This would make it easier to generate queries without needing to manually write SQL code.

To enable better match rates, the ability to write custom sort logic into the ES query would be very helpful. Reference: https://medium.com/tensult/elasticsearch-sort-by-manual-input-order-5f366b6ea31e

I want to subscribe to specific search criteria and receive the new search results via webhook message.

Enabling the use of scripting in the Person Search API will allow for more robust filtering. For example, birth_date can sometimes be in YYYY-MM-DD and other times just YYYY-MM. Current limitations wouldn't allow a user to only filter profiles with a specific date format that include day.

When sending large queries, such as bulk company lists, the 1MB limit prevents users from using more than what seems like a hard limit of 1000 domains for "job_company_website", for example. Increasing the 1MB limit may go a long way toward enabling customers to use the Person Search API for more complicated query logic and drive satisfaction + usage.

I would like the Search API to offer high throughput. We need to be able to make up to 5,000 calls per minute and return 100 profiles per call.

I would like to have a more streamlined process when using the Job Title Enrichment API in conjunction with the People Search API. Currently, it feels like a three-step process which could be more efficient.