DropfansDropfans
Help CenterFAQDevelopersMini AppSign upLog in
Acting for a creator: agencies and CRMs
Get started
Dropfans APIMake your first callConnect a creator to your appTesting without a sandboxApply for API access
Concepts
Authentication & API keysApps & approvalAPI categoriesRate limitsErrorsPagination & batch limitsModeration & statusesMoney & unitsActing for a creator: agencies and CRMs
Guides
Sell a drop end-to-endUpload images, audio and videoLinks & Telegram deep linksPost to the For You feedEarnings & balanceBroadcast one drop to many fansCreator sign-up from your platformBuild your own CRM dashboard
Webhooks
Webhooks & polling
Build with AI
Build with AIAgent prompt
API v1 (OAuth apps)
OAuth appsAPI v1 overviewAPI v1 resource listAPI v1 webhooks
API reference
API reference overview
▶Account
GETGet the account for this API keyGETGet the profile for a creatorNewPATCHUpdate the profile for a creatorNewGETGet the timezone for a creatorPUTUpdate the timezone for a creatorGETGet the subscription tier for a creatorNewPUTUpdate the subscription tier for a creatorNewGETGet the payout balance for a creator
▶Agencies
GETGet creators and personas for your agencyNewPOSTCreate an AI persona for your agencyNewPATCHUpdate an AI persona for your agencyNewDELDelete an AI persona for your agency (retire)NewPOSTReactivate an AI persona for your agencyNewPOSTCreate a creator invite for your agencyNewGETGet invites for your agency (cursor-paginated)NewDELDelete an invite for your agency (revoke)NewDELRemove a creator from your agencyNewGETGet revenue stats for your agencyNewGETGet daily earnings per creator for your agency (cursor-paginated)New
▶Creators you act for
GETGet creators you can act for (cursor-paginated)NewGETGet a creator you can act forNew
▶Vault
GETGet vault items for a creator (page-paginated)POSTUpload a vault item for a creatorDELDelete a vault item for a creatorPATCHUpdate a vault item’s folder for a creatorPATCHUpdate a vault item’s tags for a creatorGETGet vault folders for a creatorPOSTCreate a vault folder for a creatorDELDelete a vault folder for a creatorPOSTStart a video upload for a creator (step 1 of 3)POSTComplete a video upload for a creator (step 3 of 3)POSTCheck video status for a creator (batch)POSTCreate a media upload for a creatorNewPUTUpload a media upload part for a creatorNewPOSTComplete a media upload for a creatorNewGETGet a media upload for a creatorNew
▶Drops
POSTCreate a drop for a creatorGETGet drops for a creator (cursor-paginated)NewGETGet a drop for a creatorNewPATCHUpdate a drop for a creatorNewDELDelete (archive) a drop for a creatorNewPOSTAttach blur previews to a drop for a creatorPOSTCheck drop sales for a creator (batch)GETGet paid orders for a creator (cursor-paginated)New
▶Posts
POSTCreate a post for a creatorGETGet posts for a creator (page-paginated)GETGet a post for a creatorDELDelete a post for a creator
▶Earnings
GETGet the earnings overview for a creatorGETGet the earnings summary for a creatorNewGETGet transactions for a creator (cursor-paginated)NewGETGet paid tips for a creator (cursor-paginated)New
▶Links
GETGet links for a creatorNewPOSTCreate a link for a creatorNew
▶Telegram (advanced)
GETGet Telegram notification settings for a creatorPUTUpdate Telegram notification settings for a creatorPOSTRegister a Telegram notification chat for a creator
▶CRM integrations
POSTCreate a creator account for your appNewGETGet accounts for your app (cursor-paginated)NewGETGet an account for your appNewPOSTCreate an ID-check link for an accountNewGETGet the webhook endpoint for your appNewPUTUpdate the webhook endpoint for your appNewDELDelete the webhook endpoint for your appNewPOSTRotate the webhook signing secret for your appNewPOSTSend a test webhook event for your appNewGETGet details for your appNewGETGet dashboard stats for your appNewGETGet sales for your app (cursor-paginated)NewGETGet connected accounts for your appNew
▶Payouts
GETGet the payout summary for a creatorNewGETGet payouts for a creator (cursor-paginated)NewGETGet a payout for a creatorNewGETGet payout methods for a creatorNewPOSTCreate a Paxum payout method for a creatorNewPATCHUpdate a payout method for a creatorNewDELDelete a payout method for a creatorNewGETGet the MassPay profile for a creatorNewPOSTCreate the MassPay profile for a creatorNewGETGet MassPay wallet activation for a creatorNewPOSTCreate a payout request for a creatorNewPOSTCancel a payout request for a creatorNew
Resources
ChangelogAPI terms & acceptable use
Developers/Concepts/Acting for a creator: agencies and CRMs
Concepts

Acting for a creator: agencies and CRMs

An agency’s own key runs every creator and AI persona it manages, and an app owner’s key every account its app onboarded: call /v1/creators/{creatorId}/….

View as MarkdownUpdated Nov 1, 2026
← Previous
Money & units
Next →
Sell a drop end-to-end

Questions? support@dropfans.io

On this page
  • 1. Get the right key
  • 2. Get the account ids
  • 3. Call the creator path
  • The X-Dropfans-Account header (deprecated)
  • Permissions
  • Errors
  • Webhooks
  • Rate limits and money

Let your fans show their appreciation.

Become a creatorSign up as a fan

Company

  • Blog
  • About
  • Help & FAQ
  • Availability
  • For Creators
  • Developers

Policy

  • Terms
  • Privacy
  • Refunds
  • DMCA
  • Complaints
  • USC 2257
  • AI Content
  • Cookies

Socials

Dropfans

© 2026 Dropfans. All rights reserved.

Dropfans is operated by KVIQVIEW AB, Reg. No. 559552-3852, Gamla Låssbyvägen 27, Gothenburg, Sweden.

One key can act for many accounts by naming the creator in the path, /creators/{creatorId}/…:

  • An agency’s own key acts for every creator who accepted the agency and every AI persona it runs.
  • Your app owner’s own key acts for every account your app created with POST /accounts — as long as the account still holds the key we returned for it, bound to your app. Deleting that key (the creator can, in their dashboard) revokes your access.

Put the creator in the path: every creator endpoint (vault, drops, posts, earnings, profile, links, payout reads, …) is also served at /api/external/v1/creators/{creatorId}/<the same path>. Without it, the key acts for its own account, exactly as before. The agency endpoints, sign-up, webhooks and the CRM dashboard act as the agency or app itself and refuse a creator (400 creator_scope_not_allowed).

1. Get the right key#

The agency signs in to the Dropfans dashboard as itself (not switched into one of its creators), opens Vault → API Connect and generates a key for your app (or a Personal key for its own scripts). That is the agency’s own key. A key the agency generates while switched into a creator is that creator’s key: it stays bound to that one account.

For a CRM, use your app owner’s own key — the same one that calls POST /accounts. Keys an agency minted for its creators never act for anyone else.

2. Get the account ids#

GET /api/external/v1/creators lists every account your key can act for, with its relationship (managed, ai_persona or onboarded), your permissions on it, active (whether creator-scoped calls work for it right now) and its creatorPath. Store the ids — they never change. New personas come from POST /agency/personas, new creators join through an invite, new CRM accounts from POST /accounts.

3. Call the creator path#

# Who am I acting as?
curl "https://www.dropfans.io/api/external/v1/creators/cmh4v2q8k0003xy9z7w6v5u4t/me" \
  -H "Authorization: Bearer $AGENCY_API_KEY"

# Create a drop on that persona
curl -X POST "https://www.dropfans.io/api/external/v1/creators/cmh4v2q8k0003xy9z7w6v5u4t/drops" \
  -H "Authorization: Bearer $AGENCY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Beach set","price":25,"vaultItemIds":["clxv1a2b30001item"]}'

The request then behaves exactly as if it was sent with that account’s own key: the drop belongs to the persona, the sale is booked on the persona, the links are the persona’s. Every response carries an X-Dropfans-Account header with the id of the account it acted on — assert it if you juggle many accounts. GET /me returns key.via: agency (and the agency in key.managedBy) or app.

Send the account id only. Usernames are refused, because a username can change hands. Access is checked on every request — there is no session to set up or tear down — and a creator that cannot be honoured is always an error, never a silent fallback to your own account.

The X-Dropfans-Account header (deprecated)#

Sending X-Dropfans-Account: <account id> on the plain path does the same and keeps working. Responses to such calls carry Deprecation: true and a Link: <…/v1/creators/{id}/…>; rel="successor-version" header pointing at the path form. Sending both the path and a header that names another account is a 400 account_mismatch.

Permissions#

An agency needs the matching permission on the account, the same switches as in the dashboard (AI personas have all of them):

PermissionEndpoints
canManageVaultvault: list, upload, folders, tags, video uploads
canManageDropsdrops, orders, posts
canViewStatsearnings, tips, balance, reading the subscription tier, payouts (read only)
canEditProfileprofile and timezone changes, subscription tier, Telegram notifications
noneGET /me, GET /timezone, GET /profile, GET /links

Your app owner’s key has every permission except co-performers on the accounts your app onboarded. Each reference page names the permission it needs. Requesting or cancelling a payout and changing payout methods are never possible for another account: those endpoints refuse a creator (creator_scope_not_allowed / account_header_not_allowed) and keys an agency minted for a managed account (agency_key_not_allowed), whatever the permissions.

Errors#

StatuscodeWhen
400account_mismatchThe path names one creator and X-Dropfans-Account another.
400creator_scope_not_allowedA /v1/creators/{creatorId}/… call to an endpoint that acts as the key’s own account, agency or app.
400invalid_account_headerThe header is not an account id (e.g. a username).
403account_not_managedThe key cannot act for that account: no accepted management, not an account your app onboarded (or it no longer holds your app’s key), a key minted for one creator, or someone is suspended, banned or deleted. An unknown id gets the same answer.
403permission_deniedThe agency lacks the permission named in the permission field on that account.
400account_header_not_allowedThe header was sent to an endpoint that acts as the key’s own account, agency or app.
403agency_key_requiredAn agency endpoint was called with a key that is not a verified agency’s own key.

Webhooks#

An app that holds an agency’s own key also receives webhook events for every creator and persona that agency manages (accepted management). Those payloads carry data.agencyId next to data.accountId, so you can route them. An app is never sent the same event twice, even if it also holds that creator’s own key.

Rate limits and money#

  • Rate limits stay per key: one key acting for ten accounts shares one budget. Read the rate-limit headers and spread polling accordingly.
  • Buyers always pay on Dropfans: buy links, tip links and the subscribe sheet open the Dropfans checkout (web or Telegram Mini App), never yours. Use the links from GET /links for each creator to get each account’s own.
  • GET /balance can be negative for agency-managed accounts (internal settlements can pull a bucket below zero). Render it signed; do not clamp to zero.

Next: Sell a drop end-to-end or Connect a creator to your app.