Skip to main content
Explorium fetches businesses and prospects with a filters object. CompanyEnrich V2 search also takes a filter object, so most conditions translate one to one. The names, value formats, and a few filters differ. This page shows each pattern and the filters that have no equivalent. A translation that silently drops a condition returns, and charges for, the wrong records. Translate each filter, and check the result with the free count endpoint.

How the two search models differ

Translate a filter in four steps

1

List the filters

Write down each key in filters, with its values and whether it uses negate.
2

Map each filter

Find the pattern in the tables below. Convert values with the value translations, and look up IDs and names with the free geo, industry, keyword, technology, and position endpoints.
3

Count it for free

Send the filter to the company or people count endpoint. Compare total with the total_results you recorded from Explorium. A large gap usually means a filter was dropped or a value was not converted.
4

Fetch one page

Run the search with a small pageSize and check the records against what you expect. An empty search still costs one result’s base price.
For example, this Explorium fetch:
becomes this CompanyEnrich search:
The revenue range is wider than Explorium’s 10M-25M, so the search can return more companies. Filter revenue in your code if you need the narrower range.

Business search patterns

Prospect search patterns

Person filters such as domain, position, seniority, and department match the person’s current job. Conditions on the employer, such as its size or industry, go in a company query, which takes the company search filters.

Filters that do not translate

  • Person location below country level. People search filters by country. Filter cities and regions in your code.
  • Contact availability, skills, interests, and total experience.
  • Technology categories, Google categories, number of locations, intent topics, and events. For Google categories, try a semantic search.
  • include_related_job_titles. List the related titles yourself, or look them up with position autocomplete.
  • negate on filters without a notIn rule. Check the filter’s matching rules in the filter reference.

Totals and pagination

Search responses do not include a total. The free count endpoints return total, the number of matching records, and count, the number your plan lets you retrieve. Neither breaks the total down by segment, so run one count per segment. Pages hold 1 to 100 results, set with pageSize, against up to 500 on Explorium. Pass the nextCursor of one page as cursor to get the next, until nextCursor is omitted. A cursor expires 24 hours after the first page. There are no numbered pages.

When a description works better than filters

If your agent turned a request into Explorium filters, it can send the request itself to a semantic search instead:
Semantic search ranks results by meaning and reports the filters it inferred in interpretation. It costs 2 credits per company returned instead of 1. To replace the lookalikes enrichment, use a lookalike search, which takes up to 10 seed domains and costs 5 per company.

Migration overview

Endpoint mapping, request and response differences, and the parity check.

Field mapping

Every field, with value translations.

Company Search API filters

Every company filter and its matching rules.

People Search API filters

Every people filter and the company query.