Skip to content

Pull Linktree Profile Details Without Blocks

A Linktree profile is a small page that hides a lot of useful structure: a bio, an ordered list of outbound links, per-link click counts, social handles, theme metadata and creator details.

OUTPUT FORMATSHTMLJSONMarkdown

Collecting those fields by hand does not scale, and running your own headless browsers against a page that changes markup and defends against bots adds maintenance you probably do not want. This page explains how a managed scraping API handles the rendering, proxy rotation and anti-bot work, what each request option buys you, and how the credit costs stack up so you can decide before you build.

What a Linktree profile request returns

Each profile page can yield the same core set of fields: the profile bio, the full ordered link list, click counts for each link, the social handles a creator publishes, theme metadata, and creator details. Most Linktree work falls into one of three buckets: profile statistics, the creator's full set of outbound and social links, and profile imagery. Statistics feed competitor comparisons and trend spotting; link sets feed influencer research and cross-platform creator mapping; image URLs feed verification and branding checks.

You choose the shape of the response. Rendered HTML is the default and is the right pick when you already have a parser. Structured JSON is the right pick when the fields feed a database or dashboard. Screenshots and Markdown are separate output modes for visual checks and LLM-ready text respectively.

Request options and what each one changes

The API is a single endpoint that takes a target URL plus options. The options that matter for Linktree work:

  • render_js=true runs the page in a real headless browser and returns post-render HTML. Use it when the fields you need only appear after JavaScript executes.
  • country_code routes the request through a residential IP in that country. Use it when content varies by geography.
  • extract_rules maps CSS selectors to field names and returns parsed JSON. Use it when you know the page structure and want deterministic fields.
  • ai_extract_rules takes a natural-language spec and returns parsed JSON. Use it when the structure shifts and you would rather describe the fields than maintain selectors.
  • stealth_proxy is the heavier anti-bot path for pages that block ordinary requests.
  • premium_proxy sits between the default and stealth paths and can be combined with JS rendering.

A useful failure distinction: a request that returns 200 with an empty field usually means the selector or spec did not match the rendered DOM, while a request that returns a block page or a non-200 means the anti-bot layer rejected you. Check which one you are seeing before changing options, because adding stealth_proxy to a selector mismatch just costs more credits for the same empty field.

Field-to-option map

A quick reference for which option to reach for when a field is missing or wrong:

  • Bio text missing: enable render_js, then re-check with extract_rules.
  • Link list incomplete: enable render_js; if links are lazy-loaded, a JavaScript scenario that scrolls can help.
  • Click counts missing: these are usually rendered client-side, so render_js is the first lever.
  • Social handles missing: confirm the handles are actually published on the profile, then check the selector.
  • Theme metadata missing: render_js, then ai_extract_rules if the markup is unstable.
  • Profile image URL missing: check the image selector against the rendered HTML.
  • Content differs by country: add country_code.
  • Request blocked: escalate to premium_proxy, then stealth_proxy, and expect the credit cost to rise at each step.

Credit costs and a worked example

Credits are consumed per successful request and the cost depends on the options you enable. The captured per-request costs are: 1 credit for a base request, 5 credits when JS rendering is enabled, 10 or 25 credits for premium proxies depending on whether JS rendering is off or on, and 75 credits for stealth_proxy. API credits are valid for one month and do not roll over.

Worked example: a batch of 1,000 profile pages that need JS rendering and a premium proxy costs 25 credits each, or 25,000 credits. The same batch on stealth_proxy costs 75,000 credits. If only 200 of those pages actually need the stealth path, run the other 800 at the cheaper tier and you spend 20,000 + 15,000 = 35,000 credits instead of 75,000. That split is usually the single biggest cost lever on a Linktree job.

Concurrency limits are set per plan, not per target. If Linktree throttles an aggressive pattern, space out requests or spread them across sessions rather than assuming a per-domain rate limit exists.

Choosing an output mode

Four output modes cover most Linktree pipelines:

  • Rendered HTML: best when you already have a parser and want the full page.
  • Structured JSON via extract_rules or ai_extract_rules: best when fields feed a database, dashboard or downstream model.
  • Screenshot: best for visual verification of a profile's current appearance.
  • Markdown: best when the output is going into an LLM context window and you want clean text rather than markup.

If you are unsure, start with rendered HTML and a small extract_rules spec for the three or four fields you actually need. Add ai_extract_rules only when the selector maintenance becomes the bottleneck.

Setup path

The workflow is four steps: create an account to get an API key and starting credits, install an SDK or use plain cURL, send the Linktree URL with your chosen options, then add advanced parameters as your needs grow. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack. Code samples in Python, Node.js and cURL are available in the documentation, and a request builder lets you assemble a call without writing code first.

Compliance and data handling

The service is described as GDPR and CCPA compliant and does not collect or store personal data from scraped sites unless the user explicitly requests it. That matters for Linktree work because profiles often contain personal identifiers. Treat the creator's published handles and bio as personal data in your own storage, and keep a record of why you collected each field.

Plan comparison (captured reference)
PlanPriceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT. All plans include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules. This is a captured reference; check current pricing before you buy.

Frequently asked questions

How do I handle JavaScript when scraping Linktree profile data?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you get the post-render HTML back.

Can I scrape Linktree profile data from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping Linktree profile data?

There are concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Linktree profile data?

Two routes produce parsed JSON in the response. With extract_rules you supply CSS selectors paired with the field names you want. With ai_extract_rules you describe the fields in plain language instead. Pick selectors when the markup is stable, and the natural-language spec when it is not.

Which programming languages can I use to scrape Linktree profile data?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Linktree profile data?

Signup includes 1,000 free credits with no card required, and paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.

What is the difference between a blocked request and a missing field?

A blocked request returns a block page or a non-200 status and means the anti-bot layer rejected you. A missing field on a 200 response usually means your selector or natural-language spec did not match the rendered DOM. Fix the selector first, and only escalate to stealth_proxy when you are actually being blocked.