Changelog

​

Professional-network name and normalized title on Person profiles

• basic_profile.professional_network_name — the display name on the person’s professional-network profile, returned by both /person/search and /person/enrich. On search it is also a filterable field (not sortable). See the search field reference and the enrich response reference.
• basic_profile.normalized_title — the normalized job-title object (matched_title, department, sub_department, similarity, confident) is now also returned by /person/enrich, matching the field already available on /person/search.

​

Normalized titles, education details, and logos on Person Search

• basic_profile.normalized_title — an object with matched_title, department, sub_department, similarity, and confident. Filter on basic_profile.normalized_title.matched_title, .department, or .sub_department (filterable, not sortable). See the field reference.
• Education location and description — each education.schools[] entry now returns a location object (raw, city, state, country, continent) and a description. The location sub-fields are filterable via education.schools.location.*. See the education fields.
• education.schools[].institute_logo_permalink — a stable Crustdata-hosted school logo URL, returned for display.
• experience.employment_details[].company_profile_picture_permalink — a stable Crustdata-hosted employer logo URL, so you can render company logos without resolving image URLs yourself. See the profile-card example.

​

Follower count on Person Search profiles

• professional_network.followers — integer follower count from the profile. Filterable and sortable: pass it in filters.conditions[].field or sorts[].field. See the filter and sort field reference.

​

Person Search: new filter operators

• (!) — fuzzy negation. Excludes profiles whose value contains the given substring (case-insensitive). Multi-word values are matched as a literal phrase, so (!) "New York" excludes profiles literally containing "New York" but not "New Yorker". To exclude on each word independently, send separate (!) conditions inside an and group. See the operator reference and a worked example.
• geo_distance accepts lat_lng. Supply explicit coordinates as [lat, lng] to skip geocoding. When both location and lat_lng are provided, lat_lng wins. See the geo_distance reference and the lat_lng example.

​

🚀 New API version: 2025-11-01

​

What’s new

• Versioned endpoints. Every call requires the x-api-version: 2025-11-01 header, so future changes ship without breaking existing integrations.
• Bearer authentication. Authorization: Bearer <key> replaces the legacy Token scheme across every endpoint.
• Structured error envelope. A consistent { error: { type, message, metadata } } shape across every endpoint.
• Cursor-based pagination. Opaque next_cursor replaces numeric offset on search endpoints.
• Match-result envelope for enrich. Enrich responses now return matches[] with a confidence_score per match.
• Nested, neutral response sections. Flat top-level keys are grouped under sections like basic_info, employee_reviews, and funding.

​

Migrating from the legacy API