A HarvestAPI alternative that keeps HarvestAPI
Datacircle passes your LinkedIn profile calls to HarvestAPI at the price HarvestAPI charges us, $3.70 per 1,000, and puts Up2Data next to it behind the same key: $1.25 per 1,000 profiles found, about a third of the price, and a profile it can't find is free.
Your HarvestAPI request stays as it is. Two things change: the host, and one header that names the provider.
HarvestAPI and Up2Data, side by side
Both behind one key and one balance, each at the price the provider charges Datacircle, nothing added:
| What | Up2Data | HarvestAPI |
|---|---|---|
| Per profile found | $0.00125 ($1.25 per 1,000) | $0.0037 ($3.70 per 1,000) |
| Profile not found | free | $0.0023: HarvestAPI bills the lookup |
| Answered from what Datacircle stored | free | free |
| Daily limit | $1 a day per account (800 profiles), with a shared daily limit for all customers | none |
| You send | a LinkedIn profile URL | a LinkedIn profile URL |
| At the same price | followers and connections, every skill with its endorsements | every section of the profile: jobs, schools, skills, certifications, recommendations, interests |
The same request, another host
curl "https://api.datacircle.dev/linkedin/profile?url=https://www.linkedin.com/in/williamhgates" \
-H "Authorization: Token $DATACIRCLE_API_KEY" \
-H "X-Data-Provider: harvestapi"The answer is HarvestAPI's own (element, status, query, ...), minus the fields about Datacircle's own HarvestAPI account, plus datacircle_meta: which provider answered, what the call cost, your balance after it. HarvestAPI answers a 200 even when it can't find the profile (element: null), and bills that lookup.
Then try Up2Data on the same profiles
curl -X POST "https://api.datacircle.dev/v1/profiles/enrich" \
-H "Authorization: Token $DATACIRCLE_API_KEY" \
-H "X-Data-Provider: up2data" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.linkedin.com/in/williamhgates"}'A private or deleted profile is a 422, not charged. Both providers' requests and answers, field by field: LinkedIn Profile API in the docs.
Questions
Is Datacircle cheaper than HarvestAPI?
For HarvestAPI's calls, you pay what HarvestAPI charges us, $3.70 per 1,000, with no markup. What is cheaper is Up2Data, behind the same key: $1.25 per 1,000 profiles found, about a third, and nothing for a profile it can't find. Bought from HarvestAPI directly, 1,000 profiles cost $6.40 with a $20 top-up and $3.20 with a $780 top-up (its pricing page, October 2026), its credits expiring after a year; through Datacircle, $3.70 from a $5 balance that never expires.
Do I have to rewrite my HarvestAPI integration?
No. Send HarvestAPI's own request to api.datacircle.dev instead of HarvestAPI's host, with your Datacircle key in Authorization and X-Data-Provider: harvestapi. The answer is HarvestAPI's own JSON, plus one datacircle_meta object with the call's cost and your balance.
Which HarvestAPI endpoints does Datacircle pass on?
The LinkedIn profile, GET /linkedin/profile, with its url parameter. Datacircle refuses any other parameter with a 400, not charged.
When should I still use HarvestAPI rather than Up2Data?
Past Up2Data's daily limit ($1 a day per account, 800 profiles), or for the sections only HarvestAPI answers: recommendations, interests, certifications, honors.
Sign up with your work email: your API key and a $5 credit that never expires are on your dashboard, with the free 10M+ U.S. B2B leads dataset.
Sign up