OnlyFans API docs

OnlyFans API: Profile — Posts by username

Retrieve detailed public Profile data from OnlyFans by a known identifier for object records, validation, and enrichment.

Use “Posts by username” after the object is known and your product needs its current public context.

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 provides available Profile fields in normalized V2 or platform-native V1 format.

When to use it

Use “Posts by username” after the object is known and your product needs its current public context.

Common use cases

Record enrichment

Attach public OnlyFans fields to known product objects.

Data validation

Verify identifiers and current public context before downstream processing.

Analytics preparation

Use object details as inputs for reports, scoring, and related requests.

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
username Yes str value Public username without the @ symbol.
cursor No str | None QVFB... Next-page cursor returned by the previous response. Omit it for the first page.

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/posts-by-username

Normalized format

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/onlyfans.com/profile/posts-by-username" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'username=value' \
  # Optional parameters:
  # --data-urlencode 'cursor=QVFB...'
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",
  "pagination": {
    "cursor": "1783267108.000000",
    "has_more": true
  },
  "search_context": {
    "username": "amouranth"
  },
  "data": {
    "posts": {
      "count": 10,
      "items": [
        {
          "url": null,
          "post_id": "2616003230",
          "text": "Be a good boy and don’t look away 🖤",
          "text_html": "<p>Be a good boy and don’t look away 🖤</p>",
          "hashtags": [],
          "emails": [],
          "published_at": "2026-07-19T20:54:26+00:00",
          "author": {
            "user_id": "16263566"
          },
          "media": {
            "images": [
              "…"
            ],
            "videos": []
          },
          "like_count": 16,
          "comment_count": null,
          "media_count": 1,
          "price": null,
          "is_pinned": null,
          "is_archived": null,
          "is_media_ready": true,
          "can_view_media": null
        },
        {
          "url": null,
          "post_id": "2614066452",
          "text": "ngl feeling rly freaky today.. if u dont believe me just dm me rq😇",
          "text_html": "<p>ngl feeling rly freaky today.. if u dont believe me just dm me rq😇</p>",
          "hashtags": [],
          "emails": [],
          "published_at": "2026-07-18T23:50:19+00:00",
          "author": {
            "user_id": "16263566"
          },
          "media": {
            "images": [
              "…"
            ],
            "videos": []
          },
          "like_count": 99,
          "comment_count": null,
          "media_count": 1,
          "price": null,
          "is_pinned": null,
          "is_archived": null,
          "is_media_ready": true,
          "can_view_media": null
        },
        {
          "_more_items": 8
        }
      ]
    }
  }
}
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 “Posts by username” 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.