LinkedIn profiles in Clay: enrich rows with the HTTP API column, no Data Credits

• A Clay plan with HTTP API integrations: Growth or Enterprise. Clay leaves them out of Free and Launch, as its pricing page shows. Growth is $495 a month, or $446 a month if you pay yearly, with 40,000 Actions a month.
• A Datacircle API key: Log in at datacircle.dev/login with your work email. Your API key is on the page once you're in. You get a $5 credit, enough for 2,105 profiles through Up2Data.
• A column named LinkedIn URL, holding URLs like https://www.linkedin.com/in/williamhgates.

Add an enrichment, pick HTTP API, and open the Configure tab. Under Select header account, click + Add account and add one header:

Clay encrypts the account and keeps it for your workspace, and you use it in both columns below. If you type the key in a column's Headers field instead, anyone who can see the column reads it in plain text. To change the key, edit the account once, under Settings, then Connections. Anyone in your workspace can pick the account for a column of their own, and you pay for each call they make: only Clay's Enterprise plan lets you choose who can use a connection. If your Datacircle key leaks, send a POST to https://api.datacircle.dev/me/api-key/reset/ with it, as our quickstart shows: you get a new key, and the old one stops working.

In the same HTTP API panel, set:

The column sends the same request as this curl command, which you can run in a terminal to check your key:

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"}'

Clay sets the Content-Type header itself. Pick the column with /: Clay's docs say a column name typed as plain text goes to the API as that text, not the row's URL. Retry on failure is on by default and resends a call at once after a 429. At Up2Data's daily limit, that second call gets the same 429, so turn Retry on failure off: the 429 then goes to the Fetchin column. The run condition skips rows with no URL, and auto-run fills each new row. Clay lets you test the column on one row before the whole table, and we bill that call like any other.

Add a formula column named Up2Data error, with the first formula of the next section. Clay's Clay.getCellErrorMessagePreview gives a failed cell's error, and nothing for a call that worked. Clay's docs show a 429 as "Clay received a 429 error from the API". Then add a second HTTP API column:

Fetchin takes 5 requests a second from all our customers together. The rate limit keeps this column from sending more, and Clay retries a 429 once. Clay checks the run condition each time Up2Data error changes, so Fetchin runs on a row once its Up2Data error holds a 429. Clay says its error text may change. If it does, the Fetchin column stops running, and the rows past Up2Data's daily limit stay failed at no charge, until you change the condition.

Add a Formula column for each name below, with its formula. Clay's formulas are JavaScript and take no Action. Type the formulas or pick each column with /:

Up2Data error
Clay.getCellErrorMessagePreview({{Up2Data}})

Job title
{{Up2Data}}?.data?.current_company?.title || {{Fetchin}}?.jobTitle

Company
{{Up2Data}}?.data?.current_company?.name || {{Fetchin}}?.companyName

Location
{{Up2Data}}?.data?.location?.raw || {{Fetchin}}?.location

Headline
{{Up2Data}}?.data?.headline || {{Fetchin}}?.title

Each of the last four takes Up2Data's field, or Fetchin's past the daily limit, and stays empty when neither found the profile. Clay's formula preview shows nothing for Up2Data error: the column fills once you save. Our LinkedIn Profile API page shows the profile's other fields, such as jobs and schools: click a cell of the Up2Data column to see them all.

Up2Data takes $1 a day per account (421 profiles), with a shared daily limit for all customers, then answers 429 until 00:00 UTC. HarvestAPI has no daily limit. Fetchin has no daily limit either. A call your balance can't cover answers 402. Add funds, from $5, on your dashboard.

Clay keeps running the other rows when a cell fails. Open Clay's Errored rows view, in the view menu at the top of the table, to see each row with a failed cell. Click a red cell to read its error. The view also lists rows where Up2Data failed with a 429 and Fetchin then filled the job title.

To rerun rows, select them, right click, and pick Run [N] rows. Rerun a 401 once you fix the key in the account, a 402 once you've added funds, a 502, 503 or 504, and Fetchin's 429. A cell with no answer may already be billed, if the provider answered after Clay stopped waiting: your balance shows the charge, and we bill a rerun like any other call. Don't rerun a 422 or a Fetchin 404: the profile is private or deleted, and Fetchin bills each lookup. For a 400, fix the URL in the row. With Clay's Keep existing results on, the default for a new table, auto-run reruns a failed cell when its row changes.

We charge your balance the prices on our pricing page, with no markup:

If 1,000 new rows come in one day and the providers find every profile, you pay us $1.86 at most: $1.00 for 421 through Up2Data and $0.86 for the other 579 through Fetchin. Fetchin costs less per profile found but bills profiles it can't find. Up2Data doesn't, so trying Up2Data first costs less only when more than about 37% of your URLs are private or deleted. Your Clay table tries Up2Data first because you may not know how many of your URLs are gone. If the providers find more than about 63% of yours, Fetchin alone costs less: leave out the Up2Data and Up2Data error columns, give the Fetchin column the run condition !!{{LinkedIn URL}}, and keep only Fetchin's field in each formula, like {{Fetchin}}?.jobTitle.

Clay counts 1 Action for each run of an HTTP API column and no Data Credits. Clay runs the Up2Data column on each row, and past Up2Data's daily limit the Fetchin column too, so those 1,000 rows take up to 2,000 of the Growth plan's 40,000 Actions a month, more if Clay counts its retry of a 429 as another run: its docs don't say. Clay's own LinkedIn enrichment would take 500 Data Credits per 1,000 profiles, at least $25.00 at Clay's lowest Data Credit price, plus the Actions.

The same call in n8n: LinkedIn profiles in n8n. In a Zap: LinkedIn profiles in Zapier. In a Make scenario: LinkedIn profiles in Make. In an Airtable base: LinkedIn profiles in Airtable. Clay's plans next to our prices: Clay alternative. Other vendors' prices per 1,000: LinkedIn profile API pricing compared.