Skip to main content
Use this when you need to discover exact indexed values before building a Person Search query — for filter dropdowns, input validation, dataset exploration, or guided query builders. The Person Autocomplete API returns ranked field-value suggestions so you can feed the result straight into a Person Search filter without guessing at valid values.
This endpoint returns field values, not person profiles. It also has no pagination or cursor — the limit parameter (max 100) is the only way to control result size. For a full list of distinct values you need to combine Autocomplete with progressively narrower filters scopes. To fetch person records, use Person Search or Person Enrich instead.
Mental model. The top-level field is the field whose values you want suggested — the autocomplete target. filters.field is different: it’s any Person Search filter field you use to narrow the population that autocomplete runs over. Autocomplete targets come from a fixed allowlist; filter fields come from the broader Person Search filter vocabulary.
Replace YOUR_API_KEY in each example with your actual API key. All requests require the x-api-version: 2025-11-01 header.

​
At a glance

DetailValue
EndpointPOST https://api.crustdata.com/person/search/autocomplete
AuthAuthorization: Bearer YOUR_API_KEY
API versionx-api-version: 2025-11-01 header (required)
Requiredfield (string) · query (string, may be empty)
Optionallimit (integer, 1–100, default 20) · filters (single condition or condition group)
Response{ "suggestions": [ { "value": string } ] }
Errors400 invalid request · 401 unauthorized · 500 internal
PricingFree — see Pricing.
Default rate-limit is 15 requests per minute. Send an email to gtm@crustdata.co to discuss higher limits if needed for your use case.

Recipes

Most-common values, narrow with filters, multi-value, numeric comparisons, Autocomplete → Search workflow.

Reference

Contract, operators, request parameters, autocomplete-enabled fields, implementation tips, and errors.
You want to…Use
Discover valid filter values for a fieldAutocomplete (this page)
See the distinct values a field takes, ranked by countAutocomplete with an empty query
Return actual person profiles matching filtersPerson Search
Build a type-ahead dropdown for a filter UIAutocomplete with a partial query
Build a live multi-field query that returns full rowsPerson Search

​
Quick start: discover job title values

Type-ahead lookup on a single field. Pass the user’s partial input as query and cap the dropdown size with limit. 
curl --request POST \
  --url https://api.crustdata.com/person/search/autocomplete \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "field": "experience.employment_details.current.title",
    "query": "VP",
    "limit": 5
  }'
Each suggestion includes:
  • value — the exact indexed value: the raw string stored against field in Crustdata’s person index. Use it verbatim as a Person Search filter value — two distinct indexed values (for example "VP" and "vp") are different filter keys, and substituting one for the other will return different results.
Suggestions are returned ranked by internal frequency within the (optionally filtered) population. The ranking signal itself is not returned in the response. When no values match the query (or no values exist within the filters scope), the response returns an empty array — not a 404:
No results
{
    "suggestions": []
}

​
What to do next

  • Try more patterns — see Recipes for most-common values, filtered suggestions, and the Autocomplete → Search workflow.
  • Reference — see Autocomplete reference for operators, request parameters, autocomplete-enabled fields, implementation tips, and errors.
  • Search for people — use discovered values in Person Search.
  • Enrich matches — use Person Enrich to get full profiles.