Sign in

v1

latestOpenAPI 3.0.32026-07-222085264.6 KB
Person APIs
Search APIs

Search people using filters and sorting

Search the Crustdata person database using flexible filter conditions, sorting, and cursor-based pagination. Supports filtering on hundreds of fields including job title, company, location, seniority, industry, education, and more. Use compound conditions with AND/OR logic to build complex queries. Results can be sorted and paginated using cursors.

<Note> Default `rate-limit` is 30 requests per minute. Send an email to [gtm@crustdata.co](mailto:gtm@crustdata.co) to discuss higher limits if needed for your use case. </Note>
post/person/search

Headers

x-api-version'2025-11-01' required
Example:2025-11-01

API version to use. This endpoint currently requires 2025-11-01.

Request body

limitinteger
countinteger

Alias for limit.

cursorstring nullable

Pagination cursor from a previous response's next_cursor. Omit on the first page.

return_queryboolean

Debug flag - include search query in response

previewboolean

Preview mode - return only basic fields for faster response

fieldsstring[]

Optional list of field paths to include in each returned profile. When omitted, a default set of profile fields is returned. Use dot notation for a nested field (for example experience.employment_details.current.title) or a top-level family name (for example basic_profile) to include the whole family. An unsupported value returns a 400 whose metadata.available_fields lists every selectable field.

Example request

{
  "filters": {
    "field": "experience.employment_details.current.title",
    "type": "=",
    "value": "CEO"
  },
  "limit": 1
}

Response

People matching the search criteria

next_cursorstring nullable

Opaque cursor string for fetching the next page of results. Pass this value as the cursor parameter in subsequent requests. Null when no more results are available.

total_countinteger nullable

Total number of profiles matching the search criteria across all pages

total_count_relationstring nullable

Qualifier for total_count, indicating whether it is exact or a lower bound (for example eq for an exact count or gte when the true total is at least total_count). Currently returned as null.

Example response

{
  "profiles": [],
  "next_cursor": null,
  "total_count": 0,
  "total_count_relation": null
}