Clear a stuck refresh job
Force a wedged refresh job to a terminal state so a new one can start.
Force a wedged refresh job to a terminal state so a new one can start.
The refresh routes already supersede a stale job automatically, but that is a timer — you have to wait it out, and it cannot help at all with a job that keeps re-stamping its progress while making none. This is the escape hatch for that case.
Makes no platform calls, so it costs no quota. Always returns 200; cleared says whether there was in fact something to clear, and state is the job's final state (or null).
Guide: Cached reads
Authorization
apiKey Your CRM panel API key
In: header
Path Parameters
Creator account ID of the connected account (OnlyFans or Fansly). Use GET /accounts to list connected accounts and their IDs.
Which refresh job to act on: subs (subscribers), tx (transactions), or campaigns (campaign claimers).
Value in
- "subs"
- "tx"
- "campaigns"
Response Body
application/json
curl -X POST "https://example.com/accounts/string/refresh/subs/clear"{ "cleared": true, "state": null, "success": true}