Liinks Developer Portal

Build on Liinks, the link-in-bio platform for creators and businesses. Manage profiles, blocks, themes, forms, and subscribers programmatically with the REST API — or connect an AI assistant through the Liinks MCP server and let it do the editing.

The Liinks API is in beta — endpoints and shapes may still change with notice. Feedback: hello@liinks.co.

Get an API key

1. Log in to Liinks (any paid plan; new accounts can explore free, and every subscription starts with a 14-day free trial).
2. In the dashboard, go to Admin → Settings → API Keys and create a key.
3. Send it as a bearer token: Authorization: Bearer liinks_live_<your-token>.

Keys are shown once, hashed at rest, and revocable any time from the same screen. There is no separate sandbox environment: create a free account, build a test profile, and upgrade it when you need API access.

REST API quickstart

# 1. Confirm your key works and see which account it belongs to
curl https://www.liinks.co/api/v1/me \
  -H "Authorization: Bearer liinks_live_<your-token>"

# 2. List the profiles you can manage (capture an id)
curl https://www.liinks.co/api/v1/profiles \
  -H "Authorization: Bearer liinks_live_<your-token>"

# 3. Add a link block to your page
curl -X POST https://www.liinks.co/api/v1/profiles/<profileId>/blocks \
  -H "Authorization: Bearer liinks_live_<your-token>" \
  -H "Content-Type: application/json" \
  -d '{ "type": "link", "title": "My portfolio", "url": "https://example.com" }'

Full endpoint reference: interactive docs · OpenAPI 3.1 spec

MCP server

Connect Claude, ChatGPT, Cursor, or any MCP-capable client to https://www.liinks.co/api/mcp (Streamable HTTP transport) and manage your page in natural language — “add my new podcast episode to my page”.

{
  "mcpServers": {
    "liinks": {
      "type": "http",
      "url": "https://www.liinks.co/api/mcp",
      "headers": {
        "Authorization": "Bearer liinks_live_<your-token>"
      }
    }
  }
}

Available tools:

• list_profiles — List the profiles this API key can manage
• get_profile — Read a full profile bundle: fields, styles, socials, blocks, and pages in one call
• update_profile — Update profile fields (displayName, bio, tagline, slug)
• set_styles — Update the theme: colors, fonts, background, layout
• set_socials — Replace the social-icon row (ordered list)
• add_block — Add a link, text, divider, folder, or media block
• update_block — Edit, hide/show, or move an existing block
• remove_block — Delete a block permanently
• reorder_blocks — Set the top-to-bottom block order on a page
• list_form_submissions — Read visitor form submissions, newest first
• list_subscribers — Read email subscribers, newest first
• screenshot_profile — Render the live profile to JPEGs for visual verification

Errors

Every error uses one envelope: { "error": { "code", "message", "details?" } }. Codes: validation_error (400, includes a per-field details.issues[] tree), unauthorized (401), plan_required (402), forbidden (403), not_found (404), conflict (409), rate_limited (429), server_error (500). The full error schema is in the OpenAPI spec.

Rate limits

• 120 requests/minute per key (all verbs), 30 writes/minute (POST/PATCH/PUT/DELETE), rolling 60-second windows.
• Every /api/v1 response advertises the policy in RateLimit-Policy; authenticated responses carry RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset for the most constrained bucket.
• A 429 includes Retry-After and error.details.retryAfterSeconds.

Versioning & deprecation

• The API is versioned in the URL (/api/v1). Within a major version, changes are additive — new fields and endpoints may appear; existing shapes and validation only change in a new major version.
• Version-less URLs (/api/docs, /api/openapi.json, /api/mcp) always point at the current stable version; /api lists all versions with their status as JSON.
• When a version is scheduled for retirement, its responses will carry Deprecation and Sunset headers at least 180 days before shutdown, and API key owners are emailed. No version has ever been deprecated; v1 is current and stable.

Machine-readable resources

• Interactive API docs — Browsable OpenAPI reference with a built-in request runner.
• OpenAPI 3.1 specification — The canonical machine-readable contract. Generated from server schemas, always current.
• API discovery root — Lists available versions, the MCP endpoint, and the deprecation policy as JSON.
• MCP manifest — Where the MCP server lives and how to connect.
• llms.txt — Overview of Liinks for AI agents, with links to every machine-readable surface.
• Agent skills — When-to-use guidance and step-by-step instructions for AI agents.