PILLAR · AUTO DM
OnlyFans Auto DM — Mass Messaging via API Without Getting Banned
Send welcome DMs, PPV blasts, win-back flows, and scheduled tip-day campaigns across one creator account or five hundred — from a single API. Built by agency operators with a five-year track record and zero accounts banned through correct usage of our pacing engine.
DEFINITION
What is OnlyFans auto-DM?
OnlyFans auto-DM is the practice of sending direct messages to fans on autopilot — typically welcome messages, pay-per-view offers, re-engagement flows, and scheduled campaigns — without a chatter manually typing each one. The platform itself supports mass-message and welcome-message features in its native dashboard, but those built-in tools are limited: no fine-grained segmentation, no template tokens beyond first name, no webhooks, no scheduling beyond a single send time, and no cross-account workflow for agencies.
An auto-DM API solves all of that. Instead of clicking through the OnlyFans web UI, you make HTTP calls — POST a message with a recipient query, get back a campaign ID, listen for delivery webhooks, branch on whether the fan opened or unlocked, and repeat. The Only API exposes more than 200 endpoints covering every messaging primitive — single send, mass send, scheduled send, PPV with locked media, follow-up flows, and the full segment-and-tag layer underneath. It's the same automation backbone the largest agencies build on, available as a clean REST API with sub-50ms response times and per-account session isolation.
The phrases people search for around this — “OnlyFans auto DM”, “OnlyFans mass DM”, “OnlyFans auto message”, “OnlyFans bulk message”, “OnlyFans message automation” — all describe the same underlying capability: programmatic, segmented, paced outbound messaging at scale. Whether you call it auto-DM, mass-DM, or bulk message, what you actually want is a sender that won't look like a bot, a segmentation layer that targets the right fans, and a webhook layer that closes the loop on conversion. That's what this page covers.
USE CASES
Why creators and agencies use auto-DM
Auto-DM isn't one feature — it's six different revenue workflows that all happen to share the same send primitive. Most creators start with welcome messages and graduate to the full stack within their first month.
Welcome new subscribers
Trigger a personalised welcome DM the moment a new subscriber joins. The first 60 seconds is the highest-intent window of a fan's lifecycle — they're actively in the app, they just paid, and they're waiting for a reason to spend more. Automating that touch captures revenue that manual workflows lose to delay.
PPV blasts to the right audience
Send pay-per-view offers to a segmented slice of your fan list — not the whole roster. Filter by lifetime spend, last activity, subscription tier, or custom tag before the message ever leaves the API. The same drop sent to 500 of the right fans will outperform the same drop sent to 5,000 random ones, every single time.
Win-back lapsed fans
Auto-DM fans who haven't opened a message in 14, 30, or 60 days with a tailored re-engagement script. Recover churn revenue that would otherwise quietly disappear. A win-back flow tuned correctly typically reactivates 8–12% of dormant fans, which on a four-figure roster is real money every month.
Spend-based segmentation
Group fans into spender tiers (whales, mid, low) and route different copy and price points to each. Whales get exclusive drops at premium prices, low spenders get entry-level offers, mid-tier gets the volume play. Same engine, three audiences, three conversion rates that all beat a single one-price-fits-all blast.
Scheduled tip-day campaigns
Queue tip-menu reminders, payday specials, and weekend events to fire at the optimal hour for each fan's timezone. Schedule once, send forever. Recurring jobs survive scheduler restarts (we use APScheduler with SQLAlchemy job persistence) so a Friday-night payday flow keeps firing for as long as you want it to.
Multi-creator agency workflow
Run the same auto-DM playbook across 5, 50, or 500 connected creator accounts from a single CRM panel. Per-account session isolation, per-account quotas, central reporting and webhooks. The agency layer is the same primitive as the solo-creator layer — it just scales horizontally without re-architecture.
PLAYBOOKS
Auto-DM strategies that convert
Three patterns that consistently outperform generic blasts — with the actual subject lines, copy structure, and follow-up timing the top operators run.
PLAYBOOK 01
The 3-message welcome sequence
Triggered by the subscription.created webhook. Three messages over the first 48 hours — each with a different intent: greet, qualify, offer.
- T+0 minutes: Personal greeting using
{fan.first_name}. No price, no link. Goal: establish a real reply. - T+6 hours: Soft qualification — ask one question (location, what they're into, time zone). Tag the response.
- T+24 hours: First PPV offer at a low entry price (typically $8–$15) sized for a brand-new subscriber.
PLAYBOOK 02
Segmented PPV drop with whale carve-out
One drop, three audiences. Same media, three different prices and three different teaser lines. The whale segment gets the offer 4 hours before everyone else with a small bonus.
- Whales (lifetime spend > $500): Early access at $40 with a one-line teaser referencing their last purchase.
- Mid-tier ($100–$500): Same media, $25, sent four hours after whales.
- Entry tier (< $100): Same media, $15, with a 24-hour expiry timestamp in the copy to drive urgency.
PLAYBOOK 03
The 30-day win-back
Targets fans whose last activity timestamp is between 28 and 35 days old. The window matters — fans inside 14 days are still warm; fans past 60 days have usually churned to another creator.
- Subject: Reference the last interaction — “been a sec since you replied to that Tuesday drop…” — never a generic “miss you”.
- Copy: One sentence of context, one question. No PPV in the first message.
- Follow-up: If they reply, route to a chatter (or your own AI flow). If they don't, send one PPV at 50% of their average spend 48 hours later. Then stop.
IMPLEMENTATION
How it works in The Only API
Five steps, one POST. The whole flow runs against the same OnlyFans API the rest of the platform uses — same auth, same webhooks, same session isolation.
- 01.
Connect an OnlyFans account
Register a CRM panel, then log a creator account in via /api/crm/{crm_id}/accounts/login. Sessions are persisted server-side with curl-cffi Chrome impersonation.
- 02.
Build a fan segment
Query /api/crm/{crm_id}/accounts/{of_user_id}/fans with filters (lifetime spend, tags, last seen) to get the recipient list for your auto-DM campaign.
- 03.
Compose your message with tokens
Write the message body using {fan.first_name}, {fan.tier}, {fan.last_tip} and any custom field. Templates render per recipient before sending.
- 04.
POST to /api/dm/send
Send the campaign with realistic pacing, optional PPV price, and locked media. The endpoint returns a campaign_id you can poll or subscribe to via webhook.
- 05.
Listen for delivery and unlock events
Subscribe a webhook to message.delivered, message.read, and ppv.unlocked events. Use them to trigger follow-ups, tag fans, or update your downstream CRM.
curl -X POST https://theonlyapi.com/api/dm/send \
-H "X-API-Key: sk_live_REPLACE_ME" \
-H "Content-Type: application/json" \
-d '{
"of_user_id": "509955039",
"segment": {
"tags": ["whale"],
"last_seen_within_days": 30,
"min_lifetime_spend_usd": 100
},
"message": {
"text": "Hey {fan.first_name} — dropped something new in your inbox. Unlock below.",
"price_usd": 24.99,
"locked_media_ids": ["med_8a13", "med_8a14"]
},
"pacing": {
"min_delay_seconds": 6,
"max_delay_seconds": 14,
"jitter": true
},
"schedule_at": null
}'Webhook events you'll care about
Auto-DM is half-finished without a webhook layer. The send is the easy part; reacting to what happens next is where revenue compounds. These are the events most operators wire up first:
message.delivered— fired the instant the platform accepts the send. Use it to track campaign progress and update your own dashboard.message.read— fired when the fan opens the conversation. Trigger a 24-hour follow-up if no reply lands.message.replied— the signal to route a chatter or AI flow into the conversation. These are the highest-value moments in any campaign.ppv.unlocked— fan paid. Auto-tag them as a converter, add to a VIP segment, queue an upsell at T+72h.ppv.expired— fan didn't buy in time. Use it to sweep up missed revenue with a small-discount re-offer or to clean up your reporting.
Every event payload is HMAC-SHA256 signed and retried on a [5s, 30s, 5m, 30m, 2h] backoff if your endpoint returns a non-2xx. Endpoints that hard-fail repeatedly auto- deactivate so a misconfigured webhook never blocks the rest of your queue.
SAFETY
Avoiding bans
No automation tool can promise “ban-proof” — anyone who says otherwise is selling. What we can promise is a stack built specifically to make automated traffic look like the same thing a fast chatter would produce. Here's what that means in practice:
- 01.
Realistic-pace sending
Default jitter of 6–14 seconds between messages, with longer pauses every 200–400 sends. Mechanical, evenly spaced bursts are the single biggest signal anti-spam systems look for.
- 02.
Segmented audiences, not entire fan list
Sending the same message to 10,000 fans in one shot looks like spam. Sending to a 600-fan whale segment, then a different 2,000-fan mid-tier segment two hours later, looks like a real campaign manager working their list.
- 03.
Personalisation tokens on every send
First-name and last-tip tokens render server-side, so each recipient gets a unique-looking message body even on a large blast. Identical text across thousands of recipients is a fingerprint. Personalised text is not.
- 04.
Per-account session isolation + dedicated proxies
Each connected creator account gets its own session file, Chrome 136 fingerprint via curl-cffi, and an optional dedicated residential proxy. Sessions never cross-pollute, and IPs never get re-used across accounts.
- 05.
Per-account throttling + monthly quota
Hard caps prevent runaway scripts. If a webhook handler bug accidentally tries to fire 50,000 DMs in a minute, the quota layer catches it before the platform does.
- 06.
Five-year track record
The pacing and session stack has been live across thousands of connected accounts since 2020. Realistic pacing reduces ban risk — the data behind that statement is our actual operating history.
ANATOMY
What a high-converting auto-DM actually looks like
The mechanics of sending — endpoints, pacing, segmentation — are only half the equation. The other half is the message itself. Across thousands of campaigns we've seen run through the API, four structural patterns separate the messages that convert from the ones that get ignored.
Specific opener, never generic
“Hey” converts at a fraction of “Hey Sarah, saw you tipped on the Tuesday post.” Specificity is bought cheaply with template tokens — first name, last action, last spend — and pays back in open and reply rate every time.
One offer, one price, one CTA
Auto-DMs that try to do two things — sell media and ask for a tip and promote a stream — convert worse than messages that do one. Pick one outcome per send. Run the second one as a follow-up triggered by lack of response.
Price the offer to the segment, not the average
A $30 PPV will lose money on entry-tier fans and leave money on the table with whales. Use spend-based segmentation to send the same media at three different prices — and watch your aggregate revenue per send climb.
Always plan a follow-up before you send
Single-shot blasts leave roughly half the available revenue uncollected. The fans who didn't open today will open tomorrow. A two- or three-message sequence — same offer, different angles — typically lifts campaign-level revenue 30–60% over a single send. Wire the follow-up as a webhook handler on
message.reador a scheduled job 24 hours later.
FIT
Auto-DM use cases by tier
Same engine, different scale. Pick the row that matches your roster.
Solo creator
Free / Starter
- 1–3 connected accounts
- Welcome auto-DMs + scheduled tip-day blasts
- Free forever for a single account
Small agency
Growth
- 5–25 creators on a single panel
- Full segmentation + PPV blasts + win-back flows
- $15/account/month — no per-message fees
Large agency
Growth / Enterprise
- 50+ creators with isolated sessions and proxies
- Webhook automations into Slack/Discord/Make/Zapier
- Priority support, custom SLAs available
PRICING
Auto-DM is included on every plan
Free Forever for one account. Starter at $20/account/month. Growth at $15/account/month for agencies. No per-message fees, no credits, no overage. See the full breakdown, including comparison against Infloww, on the pricing page.
Related reading: the OnlyFans API homepage covers the full endpoint surface, OnlyFans automation walks through scheduled posts, fan tagging, and webhook automations beyond DMs, and The Only API vs Infloww compares us head-to-head with the largest existing dashboard product.
FAQ
Auto-DM frequently asked questions
Start sending smarter auto-DMs.
Free Forever for your first account. No credit card. All 200+ endpoints, including auto-DM, included.