Stibnite B2B Lead Enrichment API
Pricing
from $50.00 / 1,000 enriched leads
Stibnite B2B Lead Enrichment API
Find and enrich B2B people and companies with business emails, titles, LinkedIn URLs, and firmographics. Use batch runs or the Standby API for lead generation, CRM enrichment, and outbound workflows.
Pricing
from $50.00 / 1,000 enriched leads
Rating
5.0
(1)
Developer
Matt Newbill
Maintained by CommunityActor stats
1
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Stibnite Person Data API Actor
This Actor provides paid Apify access to Stibnite B2B person and company lookup. It proxies the hosted Stibnite API through a hidden Actor owner API key and bills Apify users with pay-per-event pricing.
Pricing
| Event | Price | Charged when |
|---|---|---|
person-enriched | $0.05 | One person record is delivered |
company-enriched | $0.05 | One company record is delivered |
apify-actor-start | Apify default | Automatically charged by Apify |
Zero-result requests, validation failures, upstream failures, health checks, and taxonomy calls are not charged.
Batch Modes
person_searchproxiesGET /v1/persons/searchand writes people to the default dataset.person_lookupproxiesGET /v1/persons/lookupand writes matching people.company_searchproxiesGET /v1/companies/searchand writes companies.company_peopleproxiesGET /v1/companies/{domain}/peopleand writes people.
Use maxRecords, limit, and maxPages to bound delivery. Use dedupeToken
for person search campaigns and idempotencyKey when retrying a run request.
Standby API
Standby mode exposes:
GET /healthGET /v1/persons/search/taxonomyGET|POST /v1/persons/searchGET|POST /v1/persons/lookupGET|POST /v1/companies/searchGET /v1/companies/{domain}/people
POST bodies use the same parameter names as the Stibnite API, for example:
{"q": "CMOs of SaaS companies with 50+ employees","limit": 100,"max_records": 500,"dedupe_token": "campaign-2026-q2","idempotencyKey": "request-123"}
Data Policy
The wrapper removes fields not approved for Apify v1 distribution, including mobile phone, personal email, and home address fields, before returning Standby responses or writing dataset records.