The OnlyFans API for agencies and developers — Fansly included

A real OnlyFans API request

Send a welcome DM with a vault attachment. Authentication is a single X-API-Key header. Note that crm_id, of_user_id and the fan id are path parameters, not body fields, and that write actions must be enabled once per account before a send succeeds. Message text is delivered verbatim — there is no per-fan token substitution, so personalize by sending per-fan text from your own code.

# 1. One-time per account: enable write actions.
#    Without this, sending returns 403 {"code": "WRITES_DISABLED"}.
curl -X PATCH https://theonlyapi.com/api/crm/$CRM_ID/accounts/$OF_USER_ID/polling \
  -H "X-API-Key: $YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "allow_of_write_actions": true }'

# 2. Send a welcome DM with a vault attachment.
#    price > 0 makes it a PPV; "previews" is the free teaser subset.
curl -X POST https://theonlyapi.com/api/crm/$CRM_ID/accounts/$OF_USER_ID/chats/$FAN_ID/messages \
  -H "X-API-Key: $YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hey, thanks for subscribing!",
    "mediaFiles": [987654],
    "previews": [],
    "price": 0
  }'

The same route sends on Fansly — connect a Fansly account and the request shape is unchanged.