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 + n8n

To run OnlyFans in n8n you only need one node: the HTTP Request node calls any REST API, so ofapis drops straight into your workflows. If you self-host n8n, this keeps the whole pipeline — credentials, data, logs — on infrastructure you control, which is why agencies handling multiple creators tend to prefer it over cloud-only tools.

The node you need: HTTP Request + Header Auth credential

Do not paste the token into the node. n8n has a reusable Header Auth credential that keeps it encrypted and out of exported workflows:

Credentials → New → Header Auth. Name = Authorization, Value = Bearer ofapis_sk_.... Save.
Add an HTTP Request node.
Authentication = Generic Credential Type → Header Auth, pick the credential above.
Method and URL = your ofapis endpoint.
For POSTs, set Body Content Type = JSON and turn on Send Body.

POST https://api.ofapis.com/api/public/v1/accounts/42/scheduled/posts
Content-Type: application/json

{ "mediaFiles": [88123], "scheduledAt": "2026-06-20T18:00:00Z" }

The HTTP Request node also has a built-in Import cURL button — paste any snippet from the ofapis /docs playground and it fills in method, URL, headers and body for you.

Worked example: nightly segment rebuild

Trigger: Schedule Trigger node at 03:00. Step 1 — HTTP Request GET .../accounts/42/subscribers with pagination enabled. Step 2 — an Edit Fields / Code node buckets fans by spend and last-active. Step 3 — HTTP Request POST .../accounts/42/lists/9/users to write the refreshed fan segments back. Because ofapis holds the session open server-side, the workflow never has to re-authenticate mid-run.

Three workflows to build

Vault upload → schedule. Read a file, POST it to vault media, capture the returned media id, then POST a scheduled post referencing it — a two-node content pipeline.
Webhook node → reactive flow. Use n8n's Webhook node as the target for an ofapis signed event; verify the signature in a Code node, then branch (new subscriber → welcome DM, tip → thank-you).
Win-back loop. Schedule Trigger → pull lapsed subscribers → SplitInBatches → queue a mass DM. Failed sends aren't charged, so a retry branch stays cost-safe.

FAQ

Is there a community n8n node for OnlyFans?

Not needed. The core HTTP Request node reaches every ofapis endpoint, and Header Auth keeps your Bearer token encrypted.

Does self-hosting change anything about auth?

No. The Bearer token and base URL are identical whether n8n runs on n8n Cloud or your own server; self-hosting only changes where the workflow executes and where logs live.

How do I handle paginated responses?

Enable Pagination on the HTTP Request node (or loop with SplitInBatches) and read the cursor/next-page field from the ofapis response. The OpenAPI spec documents the paging parameters per endpoint.

Where do I get a token?

Create one free; the Free plan's 250 monthly credits are enough to prototype a full workflow before upgrading.

Related: Make.com · Zapier · all integrations