Linkedin Profile Scraper: the Fetchin drop-in

Fetchin vs Linkedin Profile Scraper, feature by feature

One row deserves reading twice. The success rate an actor advertises counts a run as successful once it finishes, whether or not the dataset came back complete, so it is not the same measurement as a published availability figure. You are also buying from the individual publisher rather than from Apify: there is no SLA for this actor, no status page for it, and nothing stopping it being repriced, deprecated or abandoned.

Change the base URL, keep everything else

The official Apify client works unchanged. The actor ID, the input shape and the asynchronous run semantics all stay the same. Only the base URL and the token differ.

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
})

const run = await client
  .actor('yZnhB5JewWf9xSmoM')
  .call({ usernames: ['williamhgates'], scrapeCompany: true })

const { items } = await client
  .dataset(run.defaultDatasetId)
  .listItems()

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({
  token: process.env.FETCHIN_API_KEY,
  baseUrl: 'https://api.fetchin.io/v1/apify',
})

const run = await client
  .actor('yZnhB5JewWf9xSmoM')
  .call({ usernames: ['williamhgates'], scrapeCompany: true })

const { items } = await client
  .dataset(run.defaultDatasetId)
  .listItems()

The actor can also be referenced by its username/actor-name form, supreme_coder/linkedin-profile-scraper, if that is what your integration already passes.

Questions

Do I need to change my code?

Only the base URL and the token. The official Apify client, the actor ID yZnhB5JewWf9xSmoM and the input shape all stay the same, and the output is emulated field-by-field.

Is the output identical to supreme_coder/linkedin-profile-scraper?

Field names and structure are emulated to match. A small number of fields are per-capture tokens the source does not expose to us and are not returned. The compatibility notes in our documentation list them explicitly.

How much cheaper is it?

The actor is listed at $5.00 per 1,000 profiles on the marketplace. Fetchin bills $1.00 per 1,000 on the Starter plan, dropping to $0.90 at a million credits, with no platform usage charge on top.

How reliable is this actor?

You are buying from the individual publisher, not from Apify, so there is no SLA for the actor and no status page for it. It can be repriced, deprecated or abandoned without notice, and a pipeline built on it finds out when results stop arriving. Read the advertised success rate carefully as well: it counts a run as successful once it finishes, whether or not the dataset came back complete. Fetchin publishes one uptime figure for the whole API and exposes it at status.fetchin.io.