# Frequently Asked Questions
URL: /faq

Quick answers to common OnlyFans API questions about authentication, security, rate limits, fan analytics, webhooks, and integration best practices.

***

title: Frequently Asked Questions
description: "Quick answers to common OnlyFans API questions about authentication, security, rate limits, fan analytics, webhooks, and integration best practices."
-------------------------------------------------------------------------------------------------------------------------------------------------------------------

import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';

## API Capabilities & Features

<Accordions type="multiple">
  <Accordion title="Can your API send and read messages?" id="can-your-api-send-and-read-messages">
    Yes, our API fully supports reading and sending messages. Refer to our [List Chats](/api-reference/chats/listChats) and [Send Message](/api-reference/chats/sendMessage) endpoints for more details.
  </Accordion>

  <Accordion title="Is image generation supported?" id="is-image-generation-supported">
    Image generation is not natively supported at this time. However, we recommend third-party solutions like [fanscreator.ai](https://fanscreator.ai) for this functionality.
  </Accordion>

  <Accordion title="Can I upload media directly to the vault?" id="can-i-upload-media-directly-to-the-vault">
    Direct vault uploads aren’t supported by OnlyFans. However, you have a few options:

    * **Recommended:** Upload media exactly when and where it needs to be posted — for example, directly to a post, message, or scheduled post — instead of preloading it into the vault. This keeps your workflow simple and avoids unnecessary steps.
    * If you still want to store media in the vault ahead of time, you can:
      * Upload media using our [OnlyFans CDN upload](/api-reference/media/uploadMediaToTheOnlyFansCDN) endpoint.
      * [Create a post](/api-reference/posts/sendPost) with the media, then delete it immediately - the media will remain in your vault
      * Use our [Send Message](/api-reference/chats/sendMessage) endpoint to include the media in a message, then delete the message — again, the media will stay in your vault.
  </Accordion>

  <Accordion title="Can I integrate with Supabase or similar tools?" id="can-i-integrate-with-supabase-or-similar-tools">
    Yes! Many customers successfully use tools like [n8n](https://n8n.io) and [Supabase](https://supabase.com) for faster development and deployment.
  </Accordion>

  <Accordion title="Why do I get 404 errors on your endpoints?" id="why-do-i-get-404-errors-on-your-endpoints">
    You're likely missing the account prefix.

    * ❌ Wrong: `/api/fans/active`
    * ✅ Correct: `/api/acct_XXXXXXXX/fans/active`
  </Accordion>
</Accordions>

## Security & Safety

<Accordions type="multiple">
  <Accordion title="Is your API safe to use?" id="is-your-api-safe-to-use">
    Yes, absolutely. We have a 5-year track record with:

    * Zero accounts banned
    * Zero accounts red-flagged
    * Enterprise-grade security measures
  </Accordion>

  <Accordion title="How are login credentials protected?" id="how-are-login-credentials-protected">
    Your security is our priority:

    * All passwords and cookies are hashed in our database
    * We use OpenSSL with AES-256-CBC encryption
    * All data is signed with MAC (Message Authentication Code)
  </Accordion>

  <Accordion title="How do you handle proxy configuration?" id="how-do-you-handle-proxy-configuration">
    We implement robust proxy protection:

    * Each connected account gets a dedicated IP address
    * Public endpoints use rotating residential proxies
    * This prevents detection and ensures account safety

    For more information, refer to our dedicated [proxies guide](introduction/essentials/proxies).
  </Accordion>
</Accordions>

## API Stability & Performance

<Accordions type="multiple">
  <Accordion title="How stable is your API?" id="how-stable-is-your-api">
    Our API infrastructure includes:

    * Web Application Firewall (WAF)
    * Proxy management
    * Built-in rate limiting
    * No stability issues reported to date

    <Callout title="Please note we cannot control OnlyFans platform stability">
      Check our real-time status at: [status.onlyfansapi.com](https://status.onlyfansapi.com)
    </Callout>
  </Accordion>

  <Accordion title="What happens when OnlyFans updates their website?" id="what-happens-when-onlyfans-updates-their-website">
    Website updates have minimal impact:

    * Downtime only occurs if OnlyFans itself is down
    * We typically adapt to changes within minutes
    * No extended service interruptions
  </Accordion>
</Accordions>

## Rate Limiting & Best Practices

<Accordions type="multiple">
  <Accordion title="How do I handle rate limiting errors?" id="how-do-i-handle-rate-limiting-errors">
    **Recommended approach:** Implement exponential backoff

    1. When you receive a 429 error, wait 1 second
    2. If it happens again, double the wait time (2s → 4s → 8s)
    3. Continue up to a maximum wait time
    4. Use queuing systems like AWS SQS, Laravel Queues, or Ruby Sidekiq

    <Callout title="Need more help?">
      Email us at [hello@onlyfansapi.com](mailto:hello@onlyfansapi.com) for code examples.
    </Callout>
  </Accordion>

  <Accordion title="Where can I find rate limit documentation?" id="where-can-i-find-rate-limit-documentation">
    Rate limits are documented in our [Rate Limits](/introduction/essentials/rate-limits) guide.
  </Accordion>
</Accordions>

## API Keys Management

<Accordions type="multiple">
  <Accordion title="How many API keys should I create?" id="how-many-api-keys-should-i-create">
    **Best practice:** One API key per service/integration

    * Create separate keys for different features
    * Assign dedicated keys to external developers
    * This improves security and tracking
  </Accordion>

  <Accordion title="Is there a limit on how many API key I can create?" id="is-there-a-limit-on-how-many-api-key-i-can-create">
    No, you can create as many API keys as you want, regardless of your subscription plan.
  </Accordion>

  <Accordion title="Can one API key access multiple endpoints?" id="can-one-api-key-access-multiple-endpoints">
    Yes, a single API key can access all available endpoints.
  </Accordion>
</Accordions>

## Account Authentication & Management

<Accordions type="multiple">
  <Accordion title="Where do I find my account ID?" id="where-do-i-find-my-account-id">
    **Through our [Console](https://app.onlyfansapi.com):**

    1. Go to Dashboard -> Accounts
    2. Find the relevant account
    3. Click on the Account ID to copy it

    **Through our API:**

    1. Call our [List Accounts](/api-reference/account/listAccounts) endpoint
    2. The response includes the account ID in the `id` field

    <Callout className="pb-">
      OnlyFans API account IDs **always** start with `acct_`
    </Callout>
  </Accordion>

  <Accordion title="What's the correct format for {account} IDs in API calls?" id="whats-the-correct-format-for-account-ids-in-api-calls">
    Always use the format: `acct_XXXXXXXX`

    * Include the `acct_` prefix
    * Endpoint URL example: `https://app.onlyfansapi.com/api/acct_abc123/chats`
  </Accordion>

  <Accordion title="Can I create a platform for users to manage their accounts?" id="can-i-create-a-platform-for-users-to-manage-their-accounts">
    Yes! Use these endpoints for authentication:

    * [Start Authentication](/api-reference/connect-onlyfans-account/startAuthentication)
    * [Poll Authentication Status](/api-reference/connect-onlyfans-account/pollAuthenticationStatus)
    * Optionally, [Submit 2FA](/api-reference/connect-onlyfans-account/submit2FA)

    <Callout title="All done?" type="success">
      Use our [Get Current Account](/api-reference/account/getCurrentAccount) endpoint to retrieve the authenticated account details.
    </Callout>

    No need to use our UI - integrate these endpoints directly with your platform.
  </Accordion>
</Accordions>

## Fan Data & Analytics

<Accordions type="multiple">
  <Accordion title="Why do I sometimes get empty fan data?" id="why-do-i-sometimes-get-null-fan-data">
    This is normal behavior:

    * Chat lists return immediately
    * Fan details are scraped in the background (usually takes 2-3 seconds)

    <Callout title="Solution:" type="success">
      Either call our [Get User Details](/api-reference/users/getUserDetails) endpoint, or retry the original endpoint after 10 seconds.
    </Callout>
  </Accordion>

  <Accordion title="How can I check if a fan is online?" id="how-can-i-check-if-a-fan-is-online">
    Use the lastSeen field from our [Get Profile Details](/api-reference/public-profiles/getProfileDetails) or [Get User Details](/api-reference/users/getUserDetails) endpoints. If the `lastSeen` value is recent, the fan is likely online.

    ```json
    {
        "lastSeen": "2025-05-01T15:01:07+00:00"
        ...
    }
    ```

    <Callout title="Response may be cached, so data might be slightly outdated.">
      [-> Read more about caching](/introduction/essentials/response-structure#cache-control)
    </Callout>
  </Accordion>

  <Accordion title="How do I track fan subscription duration?" id="how-do-i-track-fan-subscription-duration">
    There's two options available:

    * **Calculate manually:** Use `subscribedOnData.subscribeAt` on endpoints like [List Active Fans](/api-reference/fans/listActiveFans) or [Get User Details](/api-reference/users/getUserDetails).
    * **Human-readable format:** Use `subscribedOnData.duration` (e.g., "3 months")
  </Accordion>

  <Accordion title="How can I see total fan spending?" id="how-can-i-see-total-fan-spending">
    Access comprehensive spending data through these fields:

    | Field            | Description                    |
    | ---------------- | ------------------------------ |
    | `totalSumm`      | Combined total of all spending |
    | `subscribesSumm` | Total spent on subscriptions   |
    | `tipsSumm`       | Total spent on tips            |
    | `messagesSumm`   | Total spent on paid messages   |
    | `postsSumm`      | Total spent on paid posts      |
    | `streamsSumm`    | Total spent on streams         |

    <Callout title="Useful endpoints:">
      * [Get User Details](/api-reference/users/getUserDetails)
      * [List Active Fans](/api-reference/fans/listActiveFans)
    </Callout>
  </Accordion>

  <Accordion title="Can I detect a fan's language preference?" id="can-i-detect-a-fans-language-preference">
    Sadly, OnlyFans doesn't store language preferences. Workaround:

    1. Fetch chat messages from the fan
    2. Use a third-party language detection API
    3. Store the detected language in your database
  </Accordion>

  <Accordion title="How do I see what content a fan has purchased?" id="how-do-i-see-what-content-a-fan-has-purchased">
    No direct endpoint exists, but you can:

    1. Retrieve chat messages using the [List ChatMessage](/api-reference/chats/listChatMessage) endpoint
    2. Check if `isOpened = true` AND `price > 0`, which indicates a purchased PPV
  </Accordion>
</Accordions>

## Webhooks & Media Handling

<Accordions type="multiple">
  <Accordion title="How do webhooks work?" id="how-do-webhooks-work">
    * 📚 Documentation: [docs.onlyfansapi.com/webhooks](/webhooks)
    * 🎥 Video Demo: [cap.so/s/p2wfkj072yt2x96](https://cap.so/s/p2wfkj072yt2x96)
  </Accordion>

  <Accordion title="Why do media in webhooks have no URL?" id="why-do-media-in-webhooks-have-no-url">
    When `"isReady": false`, the media is still processing.

    **Solution:**

    1. Get the chat ID from the webhook
    2. Poll the [List ChatMessage](/api-reference/chats/listChatMessage) endpoint every 10-20 seconds
    3. Wait for `"isReady": true`
    4. The URL will then be available

    **Alternatively:** Scrape and store vault content internally for reverse searching by media ID, once the media is ready.
  </Accordion>

  <Accordion title="Can I use webhooks with no-code tools?" id="can-i-use-webhooks-with-no-code-tools">
    Yes, you can use webhooks with no-code tools like Make, n8n or Zapier. Just set up a webhook listener in your tool and configure it to receive data from our API.

    <Callout title="Want to get started in no time?">
      We have most webhook events available as Make and Zapier modules, which you can find in our [Make](/integrations/make/available-modules#instant-triggers) and [Zapier](/integrations/zapier/available-modules#instant-triggers) directories.
    </Callout>
  </Accordion>
</Accordions>