Linktree Data API Supported API

Linktree Data API for link-in-bio discovery

Use Linktree profile and directory API methods to enrich creator, brand, and landing-page datasets with a lightweight API surface.

Start with API API method pricing Open docs

ScrapeStorm is not affiliated with Linktree. Process only data you are allowed to use.

Use cases

What you can build

Linktree coverage focuses on profile and directory groups currently available in the catalog.

Creator enrichment

Resolve link-in-bio profile details for creator databases and partnership workflows.

Directory discovery

Support discovery products that need structured profile and directory signals.

Cross-platform joining

Use Linktree data to connect social identities, owned pages, and campaign destinations.

Entity directory

All supported entities

Browse every supported Linktree entity below, understand what each surface is for, and open the exact docs that matches your workflow.

Linktree profile data

1 API method

Profile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.

What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.

API methods inside this entity 1 API method

Open the API method that matches the lookup, feed, summary, or discovery job you need.

Profile: Info by username

Open docs

Open these docs for a fast public snapshot of profile data before expanding into deeper monitoring or enrichment flows.

Linktree directory data

1 API method

Directory-style API methods expose broader reference datasets that help structure search, geo, or catalog workflows.

What you get. This entity fits products that need public lookup lists, reference coverage, and faster pathfinding before hitting more specific API methods.

API methods inside this entity 1 API method

Open the API method that matches the lookup, feed, summary, or discovery job you need.

Directory: Users by category

Open docs

Use these docs to work with directory: Users by category when your product needs a clear API method into public directory workflows.

Launch path

How teams move from evaluation to launch

Each platform page follows the same decision path: choose the data surface, inspect the docs, validate the response, then scale with pricing and status visibility.

01

Map the platform surface

Use the coverage map to identify the entity group that matches your product workflow.
02

Open representative docs

Review the implementation docs for method, path, query parameters, and response shape.
03

Normalize into your product model

Prefer V2 API methods when you need stable fields across dashboards, scoring, or enrichment jobs.
04

Monitor price and status

Check API method pricing and operational status before moving a workflow into production.

Start here

First request

Use the sample API method to verify request structure, then open the docs for identifiers and response fields.

Open docs Open mock API reference API method pricing

API method Profile: Info by username

Request cost 2 credits

Required parameters

usernamestr

GET /api/v2/linktr.ee/profile/info-by-username

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/linktr.ee/profile/info-by-username" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'username=value'

Auth header X-API-Key

Required parameters username

Billing event 2 credits per successful response

Launch details

Pricing, monitoring, and launch details

Linktree methods are priced in credits per successful response and listed in the API method pricing table.

ScrapeStorm is not affiliated with Linktree. Process only data you are allowed to use.

API methods2

Entities2

Credits2 credits

Per-success credit pricing

API method prices are visible before integration and credits are tied to successful API responses.

API reference and implementation docs

Each platform page links to the API reference and implementation docs for exact request and response details.

Responsible data use

ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.

Credit model 2 credits per successful response API reference linktr.ee Open API reference Health status 2 API methods Check API status

Adjacent APIs

Related platform data APIs

View all platforms

Details

Questions before launch

These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.

Coverage 2 entities

Credits 2 credits

Health status Check API status

Why is the public domain linktr.ee?

ScrapeStorm keeps the internal slug as linktree while API paths use the public platform domain linktr.ee.

Can I combine Linktree with social platform data?

Yes. Linktree API methods use the same authentication and response conventions as other ScrapeStorm platform APIs.