Skip to content
B2BenrichA ContactLevel company

Intent data API: pull buying signals into your own stack

What an intent data API gives a GTM engineer, the kinds of signals worth pulling, and how to join them to your accounts and contacts in code.

Dag Holmen · Updated · 5 min read

View as Markdown

An intent data API tells you which companies, and sometimes which people, are researching a topic right now. The topic can be your category, a problem you solve or a competitor by name. Instead of reading those signals in a vendor dashboard, you get them as JSON and do the work yourself: join them to your accounts, score them, and send the hot ones to the right place.

That matters because a lot of buying happens before anyone talks to sales. A Gartner survey of 632 B2B buyers, published in June 2025, found 61% prefer a rep-free buying experience. If buyers research alone, their research is often the first sign you get.

B2Benrich is adding intent data to its API. The intent endpoints aren’t documented yet, so this guide covers what to pull, how to model it and how to join it to the company and contact data you can already get from the API today.

What an intent data API returns

B2B intent data comes down to one sentence: this company showed interest in this topic at this time. A useful record answers four questions.

  • Who. The company, ideally with a domain you can join on. Some signals also tie to a person.
  • What. The topic, competitor or search theme behind the activity.
  • How much. Some measure of strength, so one stray article reads differently from a week of research.
  • When. A date, so you can tell new interest from old.

Account-level intent tells you which companies to look at. Contact-level intent narrows it to the people doing the research. Most workflows start at the account level and then use a people search to find the buyers.

First-party vs third-party intent data

TypeWhere it comes fromWhat it coversWhere it lives in your stack
First-partyYour site, product, emails and adsPeople who already know youAnalytics, CRM, product events
Third-partyResearch activity across the wider web, competitor engagement and searchYour whole market, including companies that never visited youAn intent data API

Third-party intent data is what lets you see accounts before they find you. First-party data is still worth joining in. A company researching your category that also hit your pricing page this week deserves a faster response than one that only did the research.

Intent signals worth pulling

Pick topics the way you’d pick search keywords. Be specific, and split them by what they say about the buyer.

  1. Category topics. The thing you sell, in the words buyers use. "Sales engagement software" beats "sales".
  2. Problem topics. The pain behind the purchase, such as "SOC 2 compliance" for a security tool.
  3. Competitors. Research on a named competitor is one of the clearest intent signals you can get.
  4. Commercial searches. Pricing, alternatives and comparisons tell you someone is shopping, not just learning.

Keep company news like funding and hiring out of your intent feed. It describes capacity, not research, and it belongs in your fit criteria.

A data model that holds up

Keep intent in its own table instead of writing it onto the account record. You’ll want the history later.

  • accounts: one row per company, keyed on domain, with firmographics from enrichment.
  • intent_signals: one row per account, topic and date, with the strength value. Never overwrite, always append.
  • contacts: the buyers at each account, with title and work email.

The company domain is the join key. B2Benrich company records carry domain and a company_id, so every signal can be tied to firmographics and to the people at that company.

Join intent to your accounts in code

Here’s the shape of the job. The intent call is a placeholder until the endpoint is documented. The company lookup is a real endpoint you can call today.

const BASE = 'https://api.b2benrich.com';
const headers = { 'X-Api-Key': process.env.B2BENRICH_API_KEY, 'Content-Type': 'application/json' };

// TODO: replace with the B2Benrich intent endpoint once it's documented.
// Normalize whatever it returns into your own shape: { domain, topic, strength, seenAt }.
async function getIntentSignals(accountDomains, topics) {
  return [];
}

async function enrichCompany(domain) {
  const res = await fetch(`${BASE}/v1/enrich/companies/domain-to-company`, {
    method: 'POST',
    headers,
    body: JSON.stringify({ input: domain })
  });
  return res.json(); // { status, company_id, data }
}

const topics = ['sales engagement software', 'competitor-x alternatives'];
const signals = await getIntentSignals(['acme.com', 'globex.com'], topics);

for (const signal of signals) {
  const company = await enrichCompany(signal.domain);
  await db.intentSignals.insert({ ...signal, companyId: company.company_id });
  await db.accounts.upsert({ domain: signal.domain, companyId: company.company_id, firmographics: company.data });
}

From there, the next steps are filtering to accounts that fit your ICP, finding the buyers with the prospecting API and turning the result into an in-market account list.

Treat signals as perishable

Research windows are short. A company comparing vendors this month may have signed with one by next month. Two habits help:

  • Store seenAt on every signal and weight recent activity more than old activity when you score. Lead scoring with intent data shows one way to do the decay.
  • Re-pull on a schedule and compare against the last run. The interesting events are changes: a new topic, a jump in strength, a second competitor.

Questions to ask intent data providers

Before you wire any provider into your stack, get answers to these:

  • Where does the data come from, and how is consent handled?
  • How often is it refreshed, and how far back does each record go?
  • Is it account level, contact level or both?
  • Can you choose your own topics and competitors, or only pick from a fixed list?
  • What’s the join key? A clean domain saves you a lot of matching work.
  • How does pricing scale as you poll more accounts more often?

That last one matters for builders. Intent is something you check often, and per-call pricing punishes that. B2Benrich is one plan: unlimited API usage for $500 a month, no credits. You can re-check your whole account list on every run without doing credit math first.

Frequently asked questions

What is an intent data API?
An intent data API returns which companies, and sometimes which people, are researching a topic, competitor or search theme, as structured data you can pull into your own code, database or workflow tool.
What is the difference between first-party and third-party intent data?
First-party intent comes from your own site, product and campaigns, so it only covers people who already know you. Third-party intent data covers research across the wider web, so it shows companies looking at your category before they ever visit you.
What should I compare between intent data providers?
Ask where the data comes from, how often it’s refreshed, whether it’s account or contact level, whether you can choose your own topics, what the join key is, and how pricing scales when you poll often.
Does B2Benrich have intent data?
B2Benrich is adding intent data to its API. The intent endpoints aren’t documented yet. Company and contact enrichment and search are available today, and you can build the rest of the workflow around them now.
How do I join intent data to my CRM accounts?
Use the company domain as the join key. Store signals in their own table with the domain, topic, strength and date, then match them to account records that carry the same domain.

Sources

  1. Gartner — Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience (2025)

Get your API key.

Sign up, make your first call and start building your lists.

We’ll email you a link to log in. · Read the docs