# Linktree Profile & Contact Scraper (`plowdata/linktree-profile-scraper`) Actor

Extract Linktree profiles, emails, phone numbers, social links, bios, and profile metadata. Start from URLs or usernames, or enable crawling to discover related profiles from a small seed list.

- **URL**: https://apify.com/plowdata/linktree-profile-scraper.md
- **Developed by:** [Frederic](https://apify.com/plowdata) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 15 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.003 / profile

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 🌳 Linktree Profile Scraper

Extract structured information from **specific public Linktree profiles supplied by you**.

Provide one or more Linktree profile URLs or usernames and start the Actor. Each requested profile is processed independently and returned as a structured record containing available profile information, contact details, social accounts, and links.

Every result includes **source provenance** linking it back to the public Linktree profile from which it was retrieved.

***

### 🔍 What can be extracted?

Depending on what the profile publicly contains, records can include:

|      Data type      | Description                                                                               |
| :-----------------: | :---------------------------------------------------------------------------------------- |
|       Identity      | Username, page title, description, and profile picture                                    |
| Contact information | Email addresses and phone numbers publicly exposed through the profile                    |
|     Social links    | Structured links to Instagram, TikTok, YouTube, Spotify, X, and other supported platforms |
|        Links        | Profile buttons with title, destination URL, type, and thumbnail                          |
|   Profile metadata  | Account tier, verification status, activity status, and country where available           |
|      Provenance     | Original Linktree profile URL, username, and retrieval timestamp                          |

The Actor processes only profiles explicitly identified by the user.

***

### ⚡ Why use this Actor?

- **User-defined profiles**
  You decide exactly which Linktree URLs or usernames are processed.

- **Structured contact information**
  Publicly listed email addresses and phone numbers are normalized into convenient top-level fields.

- **Typed social links**
  Social profiles are classified into supported platform types for easier downstream processing.

- **Phone normalization**
  Phone numbers are deduplicated and normalized to international format where possible.

- **Source provenance**
  Every record retains the original Linktree profile URL and retrieval timestamp.

- **Structured output**
  Results can be exported through Apify as JSON, CSV, Excel, XML, or consumed through its APIs.

***

### ✏️ Input

At least one profile URL or username must be supplied.

#### `urls`

A list of public Linktree profile URLs to process.

Example:

```json id="ofx16d"
{
  "urls": [
    {
      "url": "https://linktr.ee/garyvee"
    }
  ]
}
```

#### `usernames`

Alternatively, provide Linktree usernames directly:

```json id="n82urc"
{
  "usernames": [
    "garyvee"
  ]
}
```

Only the profiles identified by these inputs are processed.

***

### 🔧 Output

Each requested public profile is returned as a separate structured record.

Example:

```json id="5ufmtk"
{
  "id": 1056269512,
  "username": "example",
  "pageTitle": "Example Creator",
  "description": "Public profile description",
  "profilePictureUrl": "https://...",

  "tier": "free",
  "isVerified": false,
  "isActive": true,
  "country": "US",

  "emails": ["hello@example.com"],
  "phone": ["+14155552671"],

  "socialLinks": [
    {
      "type": "INSTAGRAM",
      "url": "https://instagram.com/example"
    }
  ],

  "links": [
    {
      "id": "12345",
      "type": "CLASSIC",
      "title": "Website",
      "url": "https://example.com",
      "thumbnail": "https://..."
    }
  ],

  "provenance": {
    "sourceUrl": "https://linktr.ee/example",
    "username": "example",
    "scrapedAt": "2026-05-09T20:00:00.000Z"
  }
}
```

Fields are populated only when the corresponding information is publicly exposed by the requested profile.

***

### 📘 Output fields

#### Identity

- `id` – Linktree profile identifier
- `username` – Profile username
- `pageTitle` – Public profile title
- `description` – Public profile description
- `profilePictureUrl` – Profile-picture URL where available

#### Contact information

- `emails` – Email addresses publicly exposed through the requested profile
- `phone` – Publicly exposed phone numbers, deduplicated and normalized where possible

#### Social accounts

`socialLinks[]` contains structured links to supported platforms such as:

- Instagram
- TikTok
- YouTube
- Spotify
- X
- LinkedIn
- Facebook
- and others

#### Profile links

`links[]` contains links exposed on the requested profile, including where available:

- title
- destination URL
- Linktree link type
- thumbnail URL

#### Profile metadata

Depending on availability:

- `tier`
- `isVerified`
- `isActive`
- `country`

#### Provenance

Every output record contains:

- `provenance.sourceUrl` – Original public Linktree profile
- `provenance.username` – Source username
- `provenance.scrapedAt` – Retrieval timestamp

This makes individual records traceable back to their source.

***

### 👤 Typical uses

- **Creator Research** – Structure information from known creator profiles
- **Profile Enrichment** – Add publicly listed social links or contact channels to existing records
- **Marketing Research** – Analyze selected profiles relevant to a campaign or project
- **Business Research** – Process known public profiles belonging to businesses or professionals
- **Workflow Automation** – Integrate specific Linktree profiles into internal tools or data workflows
- **Development** – Convert selected public profiles into predictable machine-readable records

***

### ⚖️ Responsible use

This Actor processes publicly accessible Linktree profiles explicitly identified by the user.

It does not bypass authentication, password protection, or other access controls. The Actor only extracts information that is already delivered as part of the publicly accessible profile response.

Users are responsible for ensuring that their use of the Actor and resulting information complies with applicable laws, contractual obligations, privacy requirements, and third-party rights.

***

### 💬 Support

Questions, edge cases, or unexpected results?

Open a support ticket and include the affected run ID or relevant log output so the issue can be reproduced and investigated.

# Changelog

This Actor's version history is a separate document: https://apify.com/plowdata/linktree-profile-scraper/changelog.md

# Actor input Schema

## `urls` (type: `array`):

List of Linktree profile urls to scrape, can be left empty if you provide usernames instead.

## `usernames` (type: `array`):

Provide a list of usernames here to scrape, can be left empty if you provide urls instead.

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://linktr.ee/garyvee"
    }
  ]
}
```

# Actor output Schema

## `profiles` (type: `string`):

Extracted profile information from Linktree user pages, including username, description, social links and contact information.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        {
            "url": "https://linktr.ee/garyvee"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("plowdata/linktree-profile-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [{ "url": "https://linktr.ee/garyvee" }] }

# Run the Actor and wait for it to finish
run = client.actor("plowdata/linktree-profile-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    {
      "url": "https://linktr.ee/garyvee"
    }
  ]
}' |
apify call plowdata/linktree-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plowdata/linktree-profile-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/X1mxXGHt5OfBn2IzH/builds/omDyEXw9m4etuWkaq/openapi.json