What counts as a credit?

One successful API call. If a request fails — expired session, upstream error — it isn't charged. Mass DMs are the exception: a mailing bills one credit per recipient, and you can preview the exact cost before sending.

How do I authenticate?

A Bearer token: Authorization: Bearer ofapis_sk_…. Create and revoke keys in the dashboard.

Can I manage multiple creators?

Yes. Link several accounts and address each by id under scoped routes. Account count scales with your plan.

Do you have an OpenAPI spec?

A complete OpenAPI 3.0 document and a live Swagger playground — point your generator at it for a typed client.

OnlyFans Slack Integration

Slack has no native OnlyFans app, but you don't need one. An OnlyFans Slack integration is two plumbing jobs: pushing ofapis events into Slack via an Incoming Webhook, and letting a slash command call ofapis back out. Both use generic Slack primitives, so there's no custom app to publish.

Direction 1: ofapis events → Slack Incoming Webhook

In Slack, create an app at api.slack.com/apps → Incoming Webhooks → Add New Webhook to Workspace, pick a channel, and copy the https://hooks.slack.com/services/... URL. That URL accepts a JSON body with a text field and nothing else required.

Now bridge it. Point an ofapis signed webhook at a tiny relay (a Cloudflare Worker or Lambda), verify the signature, and reshape the payload for Slack:

// ofapis new-message event → Slack channel
const e = req.body.data;
await fetch(SLACK_WEBHOOK_URL, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    text: `New DM from ${e.fan.username}: ${e.text}`
  })
});

Slack renders it instantly. Because ofapis holds the account session open server-side, events keep flowing without any re-auth cron on your side.

Direction 2: Slack slash command → ofapis

Register a Slash Command in the same Slack app (e.g. /of-dm), pointing its Request URL at your handler. Slack POSTs the command text; your handler forwards it to ofapis with the Bearer token, which never touches Slack:

# /of-dm 8123 Thanks for subscribing!
POST https://api.ofapis.com/api/public/v1/accounts/42/chats/8123/messages
Authorization: Bearer ofapis_sk_...
Content-Type: application/json

{ "text": "Thanks for subscribing!" }

Reply to Slack with a 200 and an ephemeral confirmation. Keep ofapis_sk_... in your handler's environment, not in Slack — Slack only ever sees the command text and the confirmation.

Three recipes to build

Tip alerts with context. Filter the webhook relay for tip events and post the amount plus the fan's lifetime spend (a quick subscribers lookup) so chatters know who to prioritise.
/of-blast mass DM. A slash command that fires a mass DM / mailing to a saved fan segment, with the segment name as the argument. Add a confirm step so nobody blasts by accident.
New-subscriber standup. Batch new-subscriber events and post a once-a-day digest to #growth instead of one message per join, keeping the channel readable.

Metered billing helps here: a failed call (expired session, upstream error) isn't charged, so a mistyped /of-dm costs nothing but a Slack error line.

FAQ

Is there an official OnlyFans Slack app?

No. Slack has no native OnlyFans app and ofapis is unaffiliated with OnlyFans. You wire events in through Incoming Webhooks and calls out through a slash-command handler — no published app required.

Do I need to host anything?

Only a small relay for the two directions. A single serverless function handles both webhook verification and slash-command forwarding; it can run on Cloudflare Workers, Lambda, or any host you already use.

How do I keep my API key out of Slack?

Store ofapis_sk_... in your handler's environment variables. Slack transmits only the slash-command text to your handler; the Bearer token is added server-side and never reaches the workspace.

Where do I get a token?

Create one free — the Free plan's 250 monthly credits are plenty to test both directions before upgrading on pricing.