API categories
Concepts

API categories

Each app has a switch per API category. Most are on; Payouts and Onboarding start off until we enable them for your app.

View as MarkdownUpdated Nov 1, 2026

Every endpoint belongs to exactly one API category, named on its reference page. Each approved app has a switch per category. A call to a category that is off for your app returns:

{ "error": "This app does not have the payouts API category enabled. Contact support to enable it.", "code": "api_category_disabled", "category": "payouts" }

with status 403. The switches apply to every key bound to the app — keys themselves are not scoped — and to Dropfans-operated apps too.

CategorycategoryDefaultCovers
Accountaccountalways onGET /me, profile, timezone, subscription tier. Always on.
Creator onboardingonboardingoffCreator sign-up from your page: POST/GET /accounts, KYC sessions.
Agency rosteragencyonThe agency endpoints: roster, personas, invites, roster revenue.
VaultvaultonVault items, folders, tags, video uploads.
Drops & checkout linksdropsonDrops, previews, check-status, orders.
For You postspostsonFor You posts.
LinkslinksonProfile, tip, subscribe and buy links.
Earnings & balanceearningsonEarnings, the earnings ledger, tips, GET /balance.
PayoutspayoutsoffPayout summary and history, payout methods, the MassPay wallet, payout requests.
Revenue splitssplitsonRevenue splits between partners.
Telegram notificationsnotificationsonTelegram sale notifications.
App webhookswebhooksonYour app’s webhook endpoint: set, rotate, test.
CRM dashboardcrmonYour integration dashboard: GET /crm/app, stats, transactions, accounts.

Getting a category switched on#

Write to support from the app owner’s account and say which category you need and why. Payouts can move a creator’s money, so we review that one most closely. GET /crm/app and GET /me list your app’s categories with enabled for each, so you can hide features that are off.

Personal keys#

A personal key (not bound to an app) has no switches: it can call every category for its own account, with two exceptions. App-level endpoints (onboarding, webhooks, the CRM dashboard) need your app owner’s key. Payout writes — payout requests, payout methods and the MassPay wallet setup — need an app key with Payouts on (403 app_key_required). Reading payouts works with a personal key.

Next: Apps & approval or Errors.

Questions? [email protected]