Link in BioLinktreeCreator DataInfluencer OutreachAPI Guide

Link in Bio API: Read Linktree, Komi, lnk.bio and Link.me Pages in Bulk

Read up to 50 Linktree, Komi, lnk.bio and Link.me pages per request and get bio, avatar, contact email, linked socials and every link on the page, for 0.5 credits per page.

SocQUpdated November 19, 20265 min read

The link in a creator's bio usually leads to a Linktree, Komi, lnk.bio or Link.me page. That page is where creators can list a contact email, their other social accounts, their shop, their latest video and their sponsors. If you research creators at scale, those pages are useful data and tedious to read by hand.

On 2026-11-17 SocQ launched the Link in Bio API on the new Link in Bio platform. It reads up to 50 pages per request, across all four services, and returns each one as a structured record. This guide covers the request, the fields, the price and how to use it in an outreach pipeline.

Quick answer: Send up to 50 page URLs in urls to POST /v1/link-in-bio/profile. Linktree, Komi, lnk.bio and Link.me URLs can go in the same request. Poll GET /v1/tasks/{task_id} and read one row per page from data.results.items. Each page found costs 0.5 credits ($0.0025).

What the Endpoint Returns

1 SocQ credit = $0.005.

EndpointWhat it returnsPrice
Link in Bio APIOne row per page: service, page name, display name, bio, avatar, verified badge, contact email, linked social profiles, and every link on the page with title, destination, type and thumbnail0.5 credits ($0.0025) per page found

Pages that no longer exist are skipped. The task fails with a refund only when none of the pages can be read.

Authentication and the Async Task Flow

All SocQ requests authenticate with an API key, and the same header is used for submit, task status and result requests:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Every collection runs as a background task:

submit -> task_id -> queued -> running -> succeeded
                                   \-> failed

The submit response contains data.task_id and data.status. Poll the task with that ID:

curl "https://api.socq.ai/v1/tasks/$TASK_ID?limit=50" \
  -H "Authorization: Bearer $SOCQ_API_KEY"

When status is succeeded, the response includes the first page of normalized records in data.results.items. limit defaults to 50 and goes up to 500; if has_more is true, pass results.next_cursor as cursor to read the next page. While a task is queued, running or failed, the endpoint returns task metadata without results.

An optional callback_url in the submit body makes SocQ send one POST with a task summary when the task finishes; read the records with GET /v1/tasks/{task_id}. A client-side timeout does not cancel a task, so resume with the same task ID instead of paying for a duplicate. 402 means insufficient credits; 429 means the key hit a rate or credit limit.

Provide up to 50 page URLs in urls, in the forms linktr.ee/name, name.komi.io, lnk.bio/name or link.me/name. A mixed list scraped from Instagram or TikTok bios needs no sorting first.

curl -X POST "https://api.socq.ai/v1/link-in-bio/profile" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://linktr.ee/miguelangeles",
      "https://kimkardashian.komi.io",
      "https://lnk.bio/msjennafischer",
      "https://link.me/danucd"
    ]
  }'

Billing follows the pages returned. SocQ may reserve credits based on the number of submitted URLs and settles the final charge from the actual result_count once the task finishes, returning any unused credits.

Understand the Page Record

A trimmed row from the documentation example:

{
  "id": "komi:kimkardashian",
  "platform": "link-in-bio",
  "resource": "profile",
  "type": "page",
  "url": "https://kimkardashian.komi.io",
  "service": "komi",
  "username": "kimkardashian",
  "name": "Kim Kardashian",
  "email": null,
  "social_urls": [
    "https://www.instagram.com/kimkardashian/",
    "https://www.tiktok.com/@kimkardashian",
    "https://www.youtube.com/@KUWTK"
  ],
  "links": [
    {
      "title": "Visit SKIMS",
      "url": "https://skims.social/shop-skims",
      "type": "link",
      "thumbnail_url": "https://komi-production-assets.s3-accelerate.amazonaws.com/photos/x_LQCBYzoWiel0-yrAnrF.jpg"
    }
  ],
  "links_count": 21
}

The fields you will use most:

  • id: the service and page name, such as linktree:miguelangeles. Use it as a stable key.
  • service and username: which service hosts the page and the page name on it.
  • name, text, avatar_url and is_verified: display name, bio, profile photo and whether the page carries the service's verified badge.
  • email: the contact email listed on the page, when there is one.
  • social_urls: social profiles and websites linked from the page's icons.
  • links: every link in the order shown, with title, url, type (as reported by the service, such as link or spotify_album) and thumbnail_url.
  • links_count: the number of links on the page.

The full schema is in the Link in Bio docs.

Batch a Large List

Split a long list into groups of 50 and submit one task per group. A minimal Python pattern:

import os, time, requests

API = "https://api.socq.ai/v1"
HEADERS = {"Authorization": f"Bearer {os.environ['SOCQ_API_KEY']}"}

def read_pages(urls):
    task = requests.post(f"{API}/link-in-bio/profile",
                         json={"urls": urls}, headers=HEADERS).json()
    task_id = task["data"]["task_id"]
    while True:
        time.sleep(3)
        data = requests.get(f"{API}/tasks/{task_id}",
                            params={"limit": 50}, headers=HEADERS).json()["data"]
        if data["status"] in ("succeeded", "failed"):
            return data

for i in range(0, len(all_urls), 50):
    result = read_pages(all_urls[i:i + 50])

Add HTTP status checks, bounded retries and cursor pagination before production use, and store each task_id with its input batch.

When to Use It

Outreach contact data. When a creator lists a contact email on the page, email holds it. Where it is empty, run the Influencer Email Finder API on the creator's main profile; it also checks link-in-bio pages, linked websites and other accounts.

Mapping a creator's accounts. social_urls gives you the creator's own list of profiles. Combine it with the Social Media Profile Finder when you need a confidence score. Both are covered in the Creator API guide.

Sponsor and affiliate research. links shows the shops, discount codes, brand partners and content a creator promotes right now. Track it over time and compare snapshots by collected_at.

Catalog enrichment. links_count, is_verified and the link type values help you tag and filter a creator database without opening each page.

FAQ

An API that reads link-in-bio pages, the landing pages creators put in their social bios, and returns them as structured data. SocQ's version covers Linktree, Komi, lnk.bio and Link.me.

Can I mix services in one request?

Yes. Linktree, Komi, lnk.bio and Link.me URLs can go in the same urls array, up to 50 per request.

What happens if a page has been deleted?

Pages that no longer exist are skipped and not charged. The task fails with a refund only when none of the submitted pages can be read.

Does every page include an email?

No. email is filled only when the creator lists one on the page; otherwise it is null.

How much does it cost to read 1,000 pages?

At 0.5 credits per page found, 1,000 pages cost 500 credits, or $2.50, submitted as 20 requests of 50 URLs.

LINK IN BIO API

Test the workflow with a public Link in Bio URL

Submit public inputs and receive normalized records with traceable source context.

Explore Link in Bio APIs