OnlyFans API docs

OnlyFans API: Profile — Social links by user ID

Retrieve public audience links and engagement signals around Profile on OnlyFans for research and segmentation.

Use “Social links by user ID” when your product needs to understand which accounts interact with or connect to an object.

Method GET
Entity Profile
Versions 2
What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

The response includes public accounts and available relationship or interaction signals for Profile.

When to use it

Use “Social links by user ID” when your product needs to understand which accounts interact with or connect to an object.

Common use cases

Audience research

Study public audience composition and overlaps around OnlyFans objects.

Segmentation

Build account groups for analytics and downstream enrichment.

Engagement evaluation

Enrich object metrics with public interaction data.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters
Parameter Required Type Example Description
user_id Yes str value Numeric user ID on the selected platform.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/onlyfans.com/profile/social-links-by-user-id

Normalized format

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/onlyfans.com/profile/social-links-by-user-id" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'user_id=value'
Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Verified example

This compact JSON example comes from the latest successful verification run for V2.

{
  "success": true,
  "status": "ok",
  "search_context": {
    "user_id": "16263566"
  },
  "data": {
    "links": {
      "count": 1,
      "items": [
        {
          "platform": "x",
          "label": "X",
          "username": "amouranth",
          "url": "https://twitter.com/amouranth"
        }
      ]
    }
  }
}
What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the OnlyFans platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs
FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

What data does this OnlyFans API method return?

The method performs “Social links by user ID” for Profile. The compact response example below shows the exact field structure.

Should I choose V1 or V2?

Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.

What do I need for the first request?

Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.