Back to catalog

Crustdata · People Data

Crustdata API / 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. Pricing: 0.03 credits per result, plus a per-result charge for each premium group you filter on or receive (experience, education and skills 0.1; certifications, honors, professional network signals, languages and summary 0.2; dev platform profile filters 0.8 or 2.5, filter side only). Filtering and receiving bill independently and sorting is free. A request with no fields returns experience and education, which costs 0.23 per result on the standard plan. Your account's prices are on /account/endpoints. Default rate-limit is 30 requests per minute. Send an email to gtm@crustdata.co to discuss higher limits if needed for your use case.

Live data

You are looking at the live public catalog.

unverifiedRequest shape unavailableUnverified
Published API evidence
Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

  • count body · optional

    Alias for limit. Example: 20

  • cursor body · optional

    Pagination cursor from a previous response's `next_cursor`. Omit on the first page. Example: "H4sIACIdzWkC..."

  • explain body · optional

    Explain an empty result. When true and a filters-only request returns `total_count` 0, `remarks` names the condition whose removal recovers profiles. Not the `search.explain` flag on semantic search, which returns per-hit scoring. Example: true

  • fields body · optional

    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. Each profile always includes `crustdata_person_id`, even when you do not request it. A requested field with no data for the profile is `null`. An unsupported value returns a `400` whose `met...

  • filters body · required

    Filter criteria — a single `PersonSearchCondition` or a `PersonSearchConditionGroup` combining conditions with `and`, `or`, or `all_of` (cross-element matching on nested-array fields).

  • limit body · optional
  • post_processing body · optional

    Post-processing options applied to search results (e.g., exclusions).

  • preview body · optional

    Preview mode - return only basic fields for faster response

  • return_query body · optional

    Debug flag - include search query in response

  • sorts body · optional

    Sort directives applied to matched people in order.

  • x-api-version header · optional

    Example: "2025-11-01"

No allowlisted official documentation or pricing reference is available.

Sign in to run this operation, inspect live eligibility, and see governed execution and audit evidence. Sign in.