The Only API docs
Promotions

Get promotions

OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances,…

GET
/api2/v2/promotions

OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances, /chats, /purchases, /subscribers/cached, ...) which are Fansly-aware.

Guide: The two surfaces

X-API-Key<token>

Your CRM panel API key

In: header

Query Parameters

limit?integer
Default10
offset?integer
Default0

Header Parameters

user-id*string

Creator account ID of the account to act as (e.g. 509955039). Required — omitting it returns 400 user-id header is required. Use GET /accounts to list your connected accounts. On /api2/v2/* the account must be an OnlyFans account; Fansly accounts are rejected there.

X-Proxy?string

Proxy URL — HTTP or SOCKS5 (e.g. http://user:pass@host:port or socks5://user:pass@host:port). Optional on post-connection routes, where it overrides the proxy saved at login time. Required on the connection routes (POST /accounts/login, POST /accounts/login/cookies, POST /accounts/login/verify-otp) for OnlyFans accounts; optional for Fansly.

Response Body

application/json

curl -X GET "https://example.com/api2/v2/promotions" \  -H "user-id: 509955039"
{  "success": true,  "status_code": 0,  "data": {    "items": [      {        "id": 0,        "type": "string",        "message": "string",        "rawMessage": "string",        "price": 0,        "subscribeDays": 0,        "subscribeCounts": 0,        "claimsCount": 0,        "canClaim": true,        "hasRelatedPromo": true,        "isFinished": true,        "createdAt": "2019-08-24T14:15:22Z",        "finishedAt": "2019-08-24T14:15:22Z"      }    ],    "hasMore": true  }}