Crustdata

Find companies with a hybrid text query and return company IDs. Supply search.query, set search.mode to hybrid and request crustdata_company_id. Use limit to select up to ten results per page and pass next_cursor back as cursor with the same query. The result contains companies and pagination metadata for subsequent company identification or enrichment.

Search the Crustdata person index by name. Send a single basic_profile.name text filter, request the person ID and name, and set limit to at most ten profiles. The profiles array contains the current page. Use next_cursor with the same filter for another page and use returned IDs to match profiles across your workflow.

Find indexed posts for one company using actor.crustdata_entity_id. The response provides post share URLs, dates and actor names. Set limit from zero to ten. Zero returns a count without post records. Continue with next_cursor when needed. Use this route to locate posts associated with a known company ID.

Search indexed jobs by a single job_details.title text filter. The returned job_listings contain job IDs, titles and posting URLs. Set limit to at most ten jobs per page and pass back next_cursor to continue with the same title filter. This supports monitoring open roles or collecting a focused sample of postings.

Return indexed values for a person search field such as title, location, employer or skill. Send field and a partial query to get ranked suggestions and use limit to control their number. Reuse each selected value as a person search filter. This helps recruiting forms and agents turn partial text or variant spellings into values present in the dataset.

Search one page of public web results through Crustdata. Send query, use the web source and set page to one. The results provide titles, URLs and available snippets, and success indicates whether the query completed. Use the returned links to gather references or select public pages for a separate HTML fetch.

Resolve a company name, website domain, professional profile URL or Crustdata ID to one or more company matches. Submit one identifier type per request and compare confidence scores and basic company information before selecting a record. Use the returned Crustdata company ID to deduplicate company lists, match imported records or request detailed enrichment for the selected company.

Fetch one public HTTP or HTTPS page through Crustdata. Send a single URL in urls and inspect the first item in the response array. Check the item’s http_status for the target page status and read any returned title and HTML. When the Crustdata API returns HTTP 200, the fetch attempt is billed even if the target page returns 404. Use the response to extract text or structured data from a page selected in a search or monitoring workflow.

Retrieve the basic company profile for one Crustdata company ID. The selected fields return the company ID and basic information such as its name and primary domain. Use the matches array to distinguish a resolved ID from an empty match. This route is useful after company search or identification and can update a verified company record in a CRM.

Look up one professional profile URL in Crustdata and return the matched person ID and name. Read match_status and matches for that URL to distinguish a matching profile from an unresolved one. Use the result to verify a profile reference or link it to an existing record.

Find indexed suggestions for a job search field such as title or category. Set field, enter the beginning of a value in query and use limit to control the number of suggestions. Reuse the returned value in the corresponding job filter. It supports job-search forms and helps agents normalize different ways of writing the same title or category.

Find indexed values for a company search field, such as an industry, company name or country. Set field and enter a partial query, then use limit to control the number of suggestions. Copy a returned value into the corresponding company search filter. This is useful for search forms and agents that need to resolve user wording to accepted filter values.