DropfansDropfans
Help CenterFAQDevelopersMini AppSign upLog in
OAuth apps
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/API v1 (OAuth apps)/OAuth apps
API v1 (OAuth apps)

OAuth apps

Register an OAuth app, send creators, fans or agencies through the authorization-code flow with PKCE, and keep their tokens fresh with rotating refresh tokens.

View as MarkdownUpdated Nov 2, 2026
← Previous
Agent prompt
Next →
API v1 overview

Questions? [email protected]

On this page
  • Register your app
  • Endpoints
  • 1. Send the account to the authorization endpoint
  • 2. Exchange the code
  • 3. Call the API
  • 4. Refresh
  • Token lifetimes
  • Revoke
  • Userinfo
  • Scopes
  • Errors

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.

API v1 at https://api.dropfans.io is authorized with OAuth 2.0 access tokens instead of API keys: the account (a creator, a fan or an agency) signs in on Dropfans, approves the scopes your app asks for, and your app receives a token that acts for that account. The authorization server is https://auth.dropfans.io, with OpenID Connect on top.

Register your app#

  1. Apply for API access and wait for the app to be approved.
  2. Ask the Dropfans team for an OAuth client for that app, with the redirect URIs you will use (exact https URLs; http://localhost is fine for development) and the scopes it needs.
  3. You receive a client id and a client secret. The secret is shown once: store it server-side only. If it leaks, ask for a new one; the old one stops working immediately.

Each API category of your app (chat, posts, vault, …) has its own switch on our side, so a scope you were granted can still answer 404 while its category is off for your app.

Endpoints#

EndpointPurpose
GET https://auth.dropfans.io/oauth2/authAuthorization: the account signs in and approves your scopes
POST https://auth.dropfans.io/oauth2/tokenExchange a code, or refresh a token
POST https://auth.dropfans.io/oauth2/revokeRevoke an access or refresh token (and its whole grant)
GET https://auth.dropfans.io/userinfoOpenID Connect claims of the token’s account
GET https://auth.dropfans.io/.well-known/openid-configurationDiscovery document
GET https://auth.dropfans.io/.well-known/jwks.jsonKeys that sign the id_token (RS256)
GET https://auth.dropfans.io/oauth2/sessions/logoutEnd-session endpoint

Read the endpoints from discovery rather than hard-coding them where your OAuth library supports it.

1. Send the account to the authorization endpoint#

PKCE with S256 is required for every client: create a random code_verifier, send code_challenge = BASE64URL(SHA256(code_verifier)). Requests without it, or with plain, are refused.

GET https://auth.dropfans.io/oauth2/auth?response_type=code
  &client_id=YOUR_CLIENT_ID
  &redirect_uri=https%3A%2F%2Fapp.example.com%2Fcallback
  &scope=openid%20offline_access%20read%3Aself%20read%3Achat
  &state=RANDOM_STATE
  &code_challenge=BASE64URL_SHA256_OF_VERIFIER
  &code_challenge_method=S256

redirect_uri must match a registered URI exactly. scope is space-separated; scopes your client is not allowed, or that the account type cannot hold, are left out of the grant (check scope in the token response). The account comes back to your redirect_uri with code and your state, or with error and error_description.

The code is single-use and expires after 60 seconds. Presenting a code twice revokes every token it produced.

2. Exchange the code#

Authenticate the client with HTTP Basic (client_secret_basic: client_id:client_secret, base64). It is the only client authentication method.

curl -X POST https://auth.dropfans.io/oauth2/token \
  -u "$CLIENT_ID:$CLIENT_SECRET" \
  -d grant_type=authorization_code \
  -d code="$CODE" \
  -d redirect_uri=https://app.example.com/callback \
  -d code_verifier="$CODE_VERIFIER"
{
  "access_token": "…",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "openid offline_access read:self read:chat",
  "refresh_token": "…",
  "id_token": "eyJ…"
}

refresh_token is only issued when the grant includes offline_access (or offline); id_token only with openid. Its sub is the account’s UUID, the same uuid that GET /users/me returns.

3. Call the API#

curl https://api.dropfans.io/v1/users/me -H "Authorization: Bearer $ACCESS_TOKEN"

See API v1 overview for paging, versions, errors and limits.

4. Refresh#

curl -X POST https://auth.dropfans.io/oauth2/token -u "$CLIENT_ID:$CLIENT_SECRET" \
  -d grant_type=refresh_token -d refresh_token="$REFRESH_TOKEN"

Refresh tokens rotate: every refresh returns a new access token and a new refresh token, and the one you sent stops working. Store the new pair before using it. If the same refresh token is presented again within 60 seconds (a retried request), you get the same new pair back; after that, reuse is treated as theft and the whole grant is revoked. The account then has to authorize your app again.

Token lifetimes#

TokenLifetime
Authorization code60 seconds, single use
Access token60 minutes
Refresh token30 days from issue; each refresh starts a new one
id_token60 minutes

Revoke#

curl -X POST https://auth.dropfans.io/oauth2/revoke -u "$CLIENT_ID:$CLIENT_SECRET" -d token="$TOKEN"

Revoking either token ends the grant. Webhook deliveries for that account stop as soon as no live grant of your app is left. Accounts can also disconnect your app themselves.

Userinfo#

GET /userinfo with the access token returns sub (the account UUID), plus preferred_username, name, picture, email and email_verified when the grant includes read:self.

Scopes#

System scopes: openid, offline_access, offline (openid adds an id_token; offline_access or offline adds a refresh token). API scopes, and which account types can hold them:

ScopeGrantsFanCreatorAgency
read:selfRead your profile and account details✓✓✓
read:chatRead your chats and messages✓✓✓
write:chatSend messages and manage chats✓✓✓
read:experienceRead fan-facing experiences (not served yet)✓✓✓
write:experiencePublish or unpublish fan-facing experiences (not served yet)—✓✓
read:fanRead your fans and their activity—✓✓
read:postRead your posts, comments and likes—✓✓
write:postCreate, edit and delete posts—✓✓
read:mediaRead your vault media—✓✓
write:mediaUpload and manage vault media and folders—✓✓
read:creatorRead creator profiles and the creators you manage—✓✓
write:creatorChange creator profile and settings—✓✓
read:insightsRead earnings and audience insights—✓✓
read:tracking_linksRead tracking links and who joined through them—✓✓
write:tracking_linksCreate and delete tracking links—✓✓
read:agencyRead your agency and its team——✓
write:agencyManage agency invites and team members——✓
read:payoutsSee your balance and payouts—✓✓
write:payoutsManage your payout methods and request payouts—✓✓

Each API v1 operation needs every scope listed for it in the resource list; a token without them gets 403 {"error":"Insufficient scopes"}.

Errors#

The authorization and token endpoints answer in the standard OAuth form {"error": "invalid_grant", "error_description": "…"} (invalid_request, invalid_client, invalid_grant, invalid_scope, unsupported_grant_type, access_denied, …). The token endpoint allows 120 requests a minute per client and 60 per IP address.