The Only API docs
Transactions

Transaction refresh status

Progress/state of the current or last transaction refresh job. Zero platform requests.

GET
/accounts/{of_user_id}/transactions/refresh/status

Progress/state of the current or last transaction refresh job. Zero platform requests.

Guide: Earnings & transactions

Authorization

apiKey
X-API-Key<token>

Your CRM panel API key

In: header

Path Parameters

of_user_id*string

Creator account ID of the connected account (OnlyFans or Fansly). Use GET /accounts to list connected accounts and their IDs.

Response Body

application/json

curl -X GET "https://example.com/accounts/string/transactions/refresh/status"
{  "cache": {    "by_type": null,    "consecutive_failures": 0,    "last_refreshed_at": null,    "last_tx_marker": null,    "newest": null,    "oldest": null,    "total": 0,    "total_amount": 0,    "total_net": 0  },  "success": true}

Refresh the transaction cache (async) POST

Start an async transaction sync. Returns 202 — poll GET /accounts/{of_user_id}/transactions/refresh/status or listen on GET /events/stream. Works for OnlyFans and Fansly.

List cached transactions GET

Read transactions from the local cache. Zero platform requests. OnlyFans and Fansly rows are normalized to the same shape.