Changelog

​

Technographics: filter by and enrich a company’s technology stack

• technographics field group on Enrich — request it explicitly via fields (it is never included by default) to get total_technologies, top_technologies, the full technologies list (each entry with name, category, and detection sources), and updated_at. See the field reference.
• Search filters — filter on technographics.total_technologies (also sortable), technographics.top_technologies, technographics.technologies.name, and technographics.technologies.category. Technographics values are not returned in search responses — filter, then enrich. See searchable fields.
• Autocomplete — two new company-scope fields: technology (technology names) and technology_category (category values) for discovering valid filter values.
• Access and pricing — technographics requires field-level permission on your account. It is a billed add-on: +2 credits per company that returns technographics data, on top of the base enrich cost; companies with no technographics data are not charged the add-on. The same add-on applies to Batch Company Enrich.

​

Company lookup: more accurate domain matching for large organizations

• Better matches for large organizations - a domain maps to the parent company rather than a subsidiary, an acquired company, or a showcase page. For example, amazon.com resolves to Amazon, paypal.com to PayPal, and schwab.com to Charles Schwab.
• Nothing to change - same endpoints, same request shape, and same response shape. No new fields and no confidence score to handle; matches just get better automatically.
• Biggest gains on high-volume domains - in testing across Fortune 500 US companies, top-1 accuracy by domain rose from 88% to 94%.

​

Person Search: natural-language search.query (beta)

• search.query - describe who you want in plain language; results are ranked by profile context (title, skills, company history, education, location, summary).
• search.mode - hybrid (default, blends keyword and concept matching) and semantic (concepts). For exact keyword matching, see the keyword search changelog below.
• mode - two recall modes: managed (default; the query may add constraints) and exact (your filters are hard constraints and the query only ranks within them).
• fit - each profile returns a relevance tier (strong / possible / weak) alongside total_count_relation, so you can keep only high-confidence matches.
• Not included - sorts; semantic results come back already rank-ordered by relevance.
• Pricing - Person Search parity at 0.03 credits per result, no premium for semantic ranking, and the same 30 requests/minute rate limit.

​

Person Search: keyword search with Boolean operators

• search.mode: "lexical" - keyword matching across the whole profile, for when you want exact terms to be found rather than concept ranking.
• search.query_syntax: "boolean" - read the query as a Boolean expression instead of plain text: a space means AND (every term required), | means OR, and you can combine terms for precise keyword search. Honored only with search.mode: "lexical" and top-level mode: "exact".

​

Multiple API keys on one account

• Create and name keys - add as many keys as you need at app.crustdata.com/api-keys, rename them anytime, and copy the generated cd_ key into any API or MCP request. See Authentication.
• Per-key status - ACTIVE (usable across the API and MCP), INACTIVE (blocked instantly and reversible), and DELETED (permanently retired; the account’s other keys keep working).
• Shared credits and rate limit - all keys on an account draw from one credit pool and one rate-limit bucket today, so keys separate and organize work rather than cap spend or speed per key.
• Coming next - credit balance and limits set at the individual API-key level.

​

Person Contact Enrich: business emails, personal emails, and phone numbers

• Identifiers — pass exactly one of professional_network_profile_urls (a profile URL) or business_emails to reverse-look-up a person, up to 25 values per request.
• fields — select which contact data to return: contact.business_emails, contact.personal_emails, contact.phone_numbers, and contact.websites (or contact for all). Each email entry includes its deliverability status. See the contact fields reference.
• Response — the same record shape as /person/enrich, restricted to the person_data.contact object. For higher fill rate on bulk lists, use the async Batch Contact Enrich job instead.

​

Person Search: geo_exclude filter operator

• geo_exclude takes the same value object as geo_distance: a centre given as location (geocoded server-side) or lat_lng ([lat, lng], skips geocoding), a required distance, and an optional unit (km, mi, miles, m, meters, ft, feet; defaults to km). When both location and lat_lng are supplied, lat_lng wins. See the operator reference and a worked example.

​

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