Migration guide

Proxycurl Alternative: Status and Migration

Proxycurl is shut down. Before you migrate, it helps to separate what it did from what you actually need — because GramScraper replaces only part of it.

Quick decision summary

Proxycurl is no longer available: its founder announced the shutdown after LinkedIn filed suit in January 2025. There is no drop-in "Proxycurl alternative" that does the same job, because the product's core was LinkedIn-derived people and company enrichment. Decide by workload, not by brand:

GramScraper is not for…

  • LinkedIn people or company profile enrichment.
  • Contact, email, or phone data of any kind.
  • A like-for-like replacement of Proxycurl's endpoint set.
  • Teams that need one vendor across many networks.

Where GramScraper is honestly weaker

If Proxycurl's reason for existing — structured LinkedIn-derived people and company records — matches your requirement, GramScraper does not replace it, and we will not pretend otherwise. GramScraper has no people-enrichment or contact endpoints. It covers public Instagram data (plus some TikTok routes). If your project actually needs public Instagram data, read on; if it needs professional-profile enrichment, evaluate providers built for that instead.

Disclosure: GramScraper publishes this page and sells a competing — but not equivalent — product. We state plainly which Proxycurl use cases GramScraper cannot serve, link to primary sources, and recommend validating any migration against your own required fields.

What Happened to Proxycurl

In January 2025, LinkedIn filed a lawsuit against Proxycurl. In its own shutdown announcement, the company stated it was shutting the product down and that the team had moved on to a new data platform. Its founder's later post confirms the current state directly: Proxycurl is shut down, and its old documentation, blog posts, and code samples should be treated as historical reference only.

Two practical consequences for anyone migrating:

Primary sources for this section are linked under Sources and dates.

Capability Comparison: Proxycurl (Historical) vs GramScraper (Current)

This table compares what Proxycurl historically offered with what GramScraper offers today. It is a scope comparison, not a claim that the products are substitutes — they are not, for most Proxycurl workloads.

Proxycurl column reflects published historical scope; GramScraper column reflects the live product checked September 22, 2026.
DimensionProxycurl (historical)GramScraper (current)
StatusShut down; plans no longer soldOperating; self-serve signup and paid packs
Primary data focusPeople and company records keyed off professional-profile identifiers, much of it LinkedIn-derivedPublic Instagram data as the primary focus, with TikTok routes also documented
Documented operationsPerson and company profiles, lookups, employee listing, search, and related endpointsInstagram profiles, posts, comments, hashtags, search, locations, audio, and related operations
Contact dataPart of the historical product's enrichment scopeNot offered — no email, phone, or personal-contact data, and no follower/following or liker lists
AuthenticationAPI key on the former serviceBearer token with a gs_ key from the dashboard
Free evaluationNot available (service closed)100 credits, no credit card
Published pricingCredit-based plans, no longer sold$9 / 10,000 credits; $40 / 50,000; $140 / 200,000
Credit expiryNot applicable (service closed)Purchased credits do not expire; no subscription
Likely fitHistorical onlyTeams that need public Instagram data, not professional-profile enrichment

Which Workload Are You Actually Migrating?

If you needed LinkedIn people or company enrichment

GramScraper is not a replacement. You will want a provider whose product is built around professional-profile and company data, and you should check its licensing and compliance posture carefully — Proxycurl's own shutdown stemmed from legal action over that data. Do not treat public Instagram data as a substitute for professional-network data; they answer different questions.

If you needed public social content and engagement data

Here GramScraper can be a fit for the Instagram portion of your pipeline. It returns public Instagram profile, post, comment, hashtag, search, and location data through documented endpoints, with a Bearer-token API and non-expiring credits. If you also need other networks under the same key, compare breadth: GramScraper is Instagram-first, and a multi-platform provider may suit you better.

To size cost honestly, use the Instagram scraping API pricing comparison and the GramScraper vs ScrapeCreators page, which explains how credit units differ between providers.

Verified Request Examples (curl and Node.js)

Because Proxycurl's API is offline, the examples below cover GramScraper only. They use the documented path and Bearer header; an unauthenticated request returns 401, confirming the endpoint resolves. Replace the placeholder key with one from your dashboard.

GramScraper · cURL
curl \
  "https://gramscraper.com/api/instagram/v1/user/by/username?username=natgeo" \
  -H "Authorization: Bearer gs_your_key"
GramScraper · Node.js
const res = await fetch(
  'https://gramscraper.com/api/instagram/v1/user/by/username?username=natgeo',
  { headers: { Authorization: `Bearer ${process.env.GRAMSCRAPER_API_KEY}` } }
);
const profile = await res.json();
console.log(profile);

Before migrating any real pipeline, confirm the exact fields and pagination behavior your application depends on against the current documentation, and test with public inputs that resemble production.

A Sensible Migration Sequence

  1. Write down the exact fields and operations the old integration consumed — not the vendor name.
  2. Classify each one: public Instagram content, professional-profile data, or contact data.
  3. For professional-profile or contact needs, evaluate providers built for that domain — GramScraper does not cover them.
  4. For public Instagram needs, test GramScraper on the free 100 credits with representative inputs.
  5. Project volume using the documented credit cost per operation, then pick the smallest pack that fits and grow from there.
  6. Keep the old code path behind a flag until the new one is verified in production.

Considering broader options too? Compare GramScraper vs Apify or read five Instagram scraping APIs compared.

Sources and dates

Third-party statements below are quoted or paraphrased from the named primary sources read on the date shown. Confirm current status yourself before relying on it.

Testing public Instagram data? Start with 100 free credits

Run representative inputs against the real API before spending — then continue from $9 for 10,000 non-expiring credits. If you need professional-profile enrichment, this is not the tool, and we would rather you know now.

Start free

Review current pricing, API docs, or the playground.