autocomplete
Autocomplete entity attributes.
Suggestions are derived from the values currently stored on entities the caller is allowed to read. A value only shows up while at least one entity carries it, so this endpoint reflects usage, not configuration.
To enumerate the label catalogue managed in the Label Builder (including labels that are not assigned to any entity yet, and excluding archived ones), use the Taxonomy endpoints instead: POST /v1/entity/taxonomies/classifications:search (taxonomiesClassificationsSearch) or GET /v1/entity/taxonomies/{taxonomySlug}:autocomplete (taxonomyAutocomplete).
For attribute=_tags the distinct values are aggregated across all matching entities, hits is the exact number of distinct values (capped at 1000) and results are ordered by usage. For other attributes the 1000 most recently updated entities are scanned and hits is the number of distinct values found so far.
Request
- Base URLhttps://entity.sls.epilot.io
- URLhttps://entity.sls.epilot.io/v1/entity:autocomplete
- Auth
- HTTP bearer
- or API key in header x-epilot-org-id
Query parameters
When true, anonymizes PII in the response: identifiers (names, emails, phone numbers, IBANs) are replaced with deterministic pseudonyms (stable within an org), addresses are generalized to postal code / city / country, and well-known free-text fields (e.g. note content) are redacted.
Useful for AI agents and data analysis use cases that must not access personal data.
Anonymization is forced (regardless of this parameter) when the access token was created with anonymize: true.
Input to autocomplete (case-insensitive substring match)
Autocomplete attribute
URL-friendly identifier for the entity schema
Limit results to entity schema
Maximum number of results to return
Number of distinct values to skip, for paging through results when hits exceeds size. from + size may not exceed 1000.
Response
Success
Example response
{
"hits": 1,
"results": [
"value"
]
}