Have a Question You Want Answered? Ask Us!
You can either use the
Suggest Editsbutton in the top right-hand corner of this page to ask a question or you can post your question in our Roadmap Board.
The likelihood score that we return in our Enrichment APIs represents the likelihood of the matching logic given the input parameters, so it wouldn't be relevant in the Person Search API.
The Person Search API ignores the nuances in our Person Enrichment API matching logic. We don't do any preprocessing (cleaning) of the inputs to the Person Search API, so you're almost guaranteed to have a lower match rate.
What's more, Person Search API queries and Person Enrichment API queries are structured differently. When you make a Person Enrichment API request, we have a custom-built query that takes the different input parameters and weights them differently, only returning a match in certain cases while using stack ranking in cases where there are multiple matches (for example, John Smith in San Francisco.)
Use Elasticsearch when:
- You have complicated boolean queries that require nested logic.
- You want to maximize the control that you have over text-based matching (titles, summaries and so forth.)
- You are comfortable writing Elasticsearch queries.
Use SQL when:
- You are running simple searches with only a few parameters.
- You're exclusively using ENUM parameters from our data (location, company, major and so forth.)
- You are comfortable writing SQL queries.
Yes, wildcard terms are supported. However, we have a hard limit of 20 wildcards per query. See the relevant sections for more information about the limitations in Elasticsearch and SQL search queries.
The error message that you are receiving has occurred because the query is too large and cURL can't handle the response. Calling the API with Python should alleviate this issue as Python compresses the extra space within an Elasticsearch query. Additional ways to decrease the query size are to reduce the profile count parameter from
60 for each call and to remove the
No. We haven't designed the API to exclude results by PDL ID. You could theoretically exclude by another primary-key identifier (for example, email), but you will eventually run into limitations due to our infrastructure. Unlike the persistent PDL ID, other primary key identifiers like email or LinkedIn URL are non-persistent and we cannot guarantee them across releases. Additionally, we will truncate extremely long queries in our internal logs, making it more difficult to assist you should you need technical support. At some point in the future, we will place limitations on query length and/or performance time to avoid these costly queries.
Updated 10 days ago