# Dropfans API Documentation

> Sell drops, manage a creator’s vault, post to the For You feed and read
> earnings from any software, with one dpfn_ API key per creator. Every page
> below has a Markdown twin — fetch the .md URL for a clean, plain-text edition.

## Get started

- [Dropfans API](https://www.dropfans.io/developers/get-started/overview.md): Sell drops, manage a creator’s vault, post to the For You feed and read earnings from any software, with one dpfn_ API key per creator.
- [Make your first call](https://www.dropfans.io/developers/get-started/first-call.md): One authenticated request to GET /api/external/v1/me that proves your key works.
- [Connect a creator to your app](https://www.dropfans.io/developers/get-started/connect-a-creator.md): How a third-party app obtains and safely stores a creator’s Dropfans API key.
- [Testing without a sandbox](https://www.dropfans.io/developers/get-started/testing.md): There is no sandbox — test against a creator account you control, with free drops and pending content.

## Concepts

- [Authentication & API keys](https://www.dropfans.io/developers/concepts/authentication.md): Every request carries Authorization: Bearer dpfn_… — a key acts for one account and grants the full surface; agency keys can name a managed account.
- [Apps & approval](https://www.dropfans.io/developers/concepts/apps-and-approval.md): Personal keys work immediately; apps that connect other people’s creator accounts need a one-time approval.
- [API categories](https://www.dropfans.io/developers/concepts/api-categories.md): Each app has a switch per API category. Most are on; Payouts and Onboarding start off until we enable them for your app.
- [Rate limits](https://www.dropfans.io/developers/concepts/rate-limits.md): Fixed per-minute and per-day windows per key, by tier — read the X-RateLimit-* headers rather than hardcoding.
- [Errors](https://www.dropfans.io/developers/concepts/errors.md): HTTP status meanings and the (deliberately honest) catalogue of body shapes you will see.
- [Pagination & batch limits](https://www.dropfans.io/developers/concepts/pagination.md): Two page styles, one cap of 50, and two batch endpoints that truncate silently — chunk client-side.
- [Moderation & statuses](https://www.dropfans.io/developers/concepts/moderation-and-statuses.md): Nothing posted through the API skips review — every status enum and lifecycle in one place.
- [Money & units](https://www.dropfans.io/developers/concepts/money-and-units.md): Prices go in as USD dollars; earnings and sales come out as integer cents; balance is dollars — per endpoint.
- [Acting for a creator: agencies and CRMs](https://www.dropfans.io/developers/concepts/agencies.md): 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}/….

## Guides

- [Sell a drop end-to-end](https://www.dropfans.io/developers/guides/sell-a-drop.md): From approved vault items to a paid sale: create the drop, share the link, poll for the sale, read the earnings.
- [Upload images, audio and video](https://www.dropfans.io/developers/guides/upload-media.md): Small files go through one multipart call; videos go straight to the CDN with a three-step TUS flow.
- [Links & Telegram deep links](https://www.dropfans.io/developers/guides/links-and-deep-links.md): Canonical profile, tip, subscribe and buy URLs for a creator — on the web and inside the Dropfans Telegram Mini App.
- [Post to the For You feed](https://www.dropfans.io/developers/guides/post-to-feed.md): Text, image and drop posts from a script or an agent — with the same moderation and daily cap as the composer.
- [Earnings & balance](https://www.dropfans.io/developers/guides/earnings-and-balance.md): Mirror the creator’s dashboard numbers and payout buckets inside your own product.
- [Broadcast one drop to many fans](https://www.dropfans.io/developers/guides/broadcast-one-drop.md): Send the same drop to many fans with one checkout link each, and match every payment back to the fan who paid.
- [Creator sign-up from your platform](https://www.dropfans.io/developers/guides/creator-signup.md): Let creators open their account from your own page: one API call creates it and returns the ID-check link to redirect them to.
- [Build your own CRM dashboard](https://www.dropfans.io/developers/guides/crm-dashboard.md): Pull the numbers your integration dashboard shows (revenue, commission, sales and connected accounts) into your own dashboard.

## Webhooks

- [Webhooks & polling](https://www.dropfans.io/developers/webhooks/overview.md): Signed webhooks tell your app about sales, refunds, payouts and ID-check results as they happen; polling endpoints cover the same ground as a fallback.

## Build with AI

- [Build with AI](https://www.dropfans.io/developers/build-with-ai/overview.md): Feed an agent the whole API in one shot: llms.txt, llms-full.txt, openapi.json, and a Markdown twin of every page.
- [Agent prompt](https://www.dropfans.io/developers/build-with-ai/agent-prompt.md): Copy-paste prompts that make an assistant post to the feed or sell drops correctly.

## API v1 (OAuth apps)

- [OAuth apps](https://www.dropfans.io/developers/api-v1/oauth-apps.md): 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.
- [API v1 overview](https://www.dropfans.io/developers/api-v1/overview.md): Base URL, versions, cursor and page paging, acting for a creator as an agency, error shapes, rate limits, money and ids for API v1 with OAuth tokens.
- [API v1 resource list](https://www.dropfans.io/developers/api-v1/resources.md): Every API v1 operation that is served today, with the scopes it needs and whether it also has the agency creator-path form.
- [API v1 webhooks](https://www.dropfans.io/developers/api-v1/webhooks.md): Subscribe a creator’s account to webhook topics with its OAuth token, verify the HMAC-SHA256 signature on every delivery, and test a topic on demand.

## API reference

- [API reference overview](https://www.dropfans.io/developers/reference/overview.md): Base URL, authentication, conventions and the shape of every response — read this before the endpoint pages.
- [Which creator this API key belongs to](https://www.dropfans.io/developers/reference/get-me.md): GET /api/external/v1/me — Returns the creator account behind the key, plus metadata about the key itself.
- [Read the creator’s public profile](https://www.dropfans.io/developers/reference/get-profile.md): GET /api/external/v1/profile — The creator's public profile: username, display name, bio, visibility, contact handles and images.
- [Update the creator’s public profile](https://www.dropfans.io/developers/reference/update-profile.md): PATCH /api/external/v1/profile — Partial update of the creator's public profile — send only the fields that change; `null` clears a field. Returns the whole profile.
- [Read the creator’s timezone](https://www.dropfans.io/developers/reference/get-timezone.md): GET /api/external/v1/timezone — Returns the creator's IANA timezone, defaulting to `"UTC"` when they never set one.
- [Set the creator’s timezone](https://www.dropfans.io/developers/reference/update-timezone.md): PUT /api/external/v1/timezone — Sets the creator's timezone — the same setting their dashboard uses for day bucketing.
- [Read the creator’s subscription tier](https://www.dropfans.io/developers/reference/get-subscription.md): GET /api/external/v1/subscription — The creator's subscription tier — price, interval, trial and whether it takes new sign-ups — plus the web link that opens the subscribe sheet. `tier` is null when the creator has no subscription set up.
- [Set the creator’s subscription tier](https://www.dropfans.io/developers/reference/update-subscription.md): PUT /api/external/v1/subscription — Creates or replaces the creator's subscription tier. This is a full replace: fields you leave out go back to their defaults (`trialDays` 0, no description or pitch, active).
- [The account’s payout balance](https://www.dropfans.io/developers/reference/get-balance.md): GET /api/external/v1/balance — The account's payout balance buckets in USD dollars: the creator side at the top level, plus `total` and `sides` for everything the account owns.
- [List the creators and personas you manage](https://www.dropfans.io/developers/reference/list-agency-creators.md): GET /api/external/v1/agency/creators — Every creator and AI persona the agency manages, with the account `id` to send as `X-Dropfans-Account` and the permissions the agency holds on each.
- [Create an AI persona](https://www.dropfans.io/developers/reference/create-persona.md): POST /api/external/v1/agency/personas — Creates an AI persona run by the agency and returns its account `id` — use it in `X-Dropfans-Account` straight away to fill its vault, create drops and post.
- [Rename an AI persona](https://www.dropfans.io/developers/reference/rename-persona.md): PATCH /api/external/v1/agency/personas/{id} — Changes an active persona's `username` (same rules as a creator's own username change; the old handle is kept in its history).
- [Retire an AI persona](https://www.dropfans.io/developers/reference/retire-persona.md): DELETE /api/external/v1/agency/personas/{id} — Retires a persona: its profile goes offline, the relationship becomes DEPARTED and any keys the agency minted for it stop working.
- [Reactivate a retired AI persona](https://www.dropfans.io/developers/reference/reactivate-persona.md): POST /api/external/v1/agency/personas/{id}/reactivate — Brings a retired persona back online under the agency, with the same rules as the dashboard: not while another agency runs it, not over the 8-persona cap, and never for an account Dropfans suspended.
- [Invite a creator to your agency](https://www.dropfans.io/developers/reference/create-agency-invite.md): POST /api/external/v1/agency/invites — Creates a join link that invites a real creator to be managed by the agency. The link is valid for 72 hours; with `email`, Dropfans also emails it.
- [List your agency’s invites](https://www.dropfans.io/developers/reference/list-agency-invites.md): GET /api/external/v1/agency/invites — The agency’s creator invites, newest first, each with its status: `pending`, `accepted`, `expired` or `revoked`.
- [Revoke an invite](https://www.dropfans.io/developers/reference/revoke-agency-invite.md): DELETE /api/external/v1/agency/invites/{id} — Revokes a pending invite: its join link stops working at once. Returns the invite with `status: revoked`.
- [Stop managing a creator](https://www.dropfans.io/developers/reference/end-management.md): DELETE /api/external/v1/agency/creators/{id} — Ends the agency's management of a creator or persona — the same as "Leave agreement" in the dashboard.
- [Revenue across your roster](https://www.dropfans.io/developers/reference/get-agency-stats.md): GET /api/external/v1/agency/stats — Revenue for the agency's own account plus every managed account it may see stats for (`canViewStats`), with a per-account breakdown — the same figures as the dashboard's "All creators" view.
- [Daily earnings per creator](https://www.dropfans.io/developers/reference/list-agency-earnings.md): GET /api/external/v1/agency/earnings — One row per managed creator per day with revenue, across every account you may see stats for (`canViewStats`), in integer cents. Paged with a cursor.
- [List the creators you can act for](https://www.dropfans.io/developers/reference/list-creators.md): GET /api/external/v1/creators — Every account your key can act for with /api/external/v1/creators/{creatorId}/…: the creators and AI personas your agency manages, and the accounts your app onboarded.
- [Get one creator you can act for](https://www.dropfans.io/developers/reference/get-creator.md): GET /api/external/v1/creators/{id} — One account from [GET /creators](/developers/reference/list-creators): its relationship to you, your permissions on it and whether creator-scoped calls work for it right now.
- [List your vault items — the source of media for posts](https://www.dropfans.io/developers/reference/list-vault.md): GET /api/external/v1/vault — Returns APPROVED items by default. Use an item's `id` as `vaultItemId` when creating a MEDIA post. Pass includePending=true to also see items still in moderation (their media is stripped).
- [Upload an image, small video or voice message](https://www.dropfans.io/developers/reference/upload-vault-item.md): POST /api/external/v1/vault — Uploads one file into the creator's vault as `multipart/form-data`.
- [Delete (hide) a vault item](https://www.dropfans.io/developers/reference/delete-vault-item.md): DELETE /api/external/v1/vault/{id} — Soft-deletes a vault item you own: nothing is removed from storage, the item is hidden and disappears from every list.
- [Move a vault item to a folder](https://www.dropfans.io/developers/reference/move-vault-item.md): PATCH /api/external/v1/vault/{id}/folder — Files a vault item into a folder, or unfiles it back to "All".
- [Replace a vault item’s content tags](https://www.dropfans.io/developers/reference/set-vault-item-tags.md): PATCH /api/external/v1/vault/{id}/tags — Replaces (not merges) the content tags on a vault item. Send the full list every time.
- [List vault folders](https://www.dropfans.io/developers/reference/list-folders.md): GET /api/external/v1/vault/folders — Every folder the creator has, alphabetically. **Unpaginated** — you always get the full list.
- [Create a vault folder](https://www.dropfans.io/developers/reference/create-folder.md): POST /api/external/v1/vault/folders — Creates a folder. Names are unique per creator (case-sensitive) and at most 50 characters.
- [Delete a vault folder](https://www.dropfans.io/developers/reference/delete-folder.md): DELETE /api/external/v1/vault/folders/{folderId} — Deletes a folder you own. **Non-empty folders are allowed**: the items inside are preserved and fall back to "All" (unfiled) — nothing is removed from storage. System folders (compliance archives) cannot be deleted.
- [Start a video upload (step 1 of 3)](https://www.dropfans.io/developers/reference/start-video-upload.md): POST /api/external/v1/vault/video-upload — Starts a direct-to-CDN video upload and returns presigned TUS credentials.
- [Finish a video upload (step 3 of 3)](https://www.dropfans.io/developers/reference/complete-video-upload.md): POST /api/external/v1/vault/video-upload/complete — Registers a finished TUS upload as a vault item and kicks moderation.
- [Check video transcoding status (batch)](https://www.dropfans.io/developers/reference/video-status.md): POST /api/external/v1/vault/video-status — Transcoding status + duration for a batch of video GUIDs (`bunnyStreamId` values from your vault items).
- [Start a media upload session](https://www.dropfans.io/developers/reference/create-media-upload.md): POST /api/external/v1/media/uploads — Opens an upload session for one image, video or audio file. Video gets tus credentials for a direct upload; image and audio get 3 MB part URLs to PUT.
- [Upload one part (image / audio)](https://www.dropfans.io/developers/reference/upload-media-part.md): PUT /api/external/v1/media/uploads/{id}/parts/{partNumber} — Uploads one part of an image or audio session: the raw bytes as the request body (`Content-Type: application/octet-stream`).
- [Complete a media upload](https://www.dropfans.io/developers/reference/complete-media-upload.md): POST /api/external/v1/media/uploads/{id}/complete — Turns the upload into a vault item and starts moderation. Image / audio: the parts are joined and stored with their metadata removed. Video: the finished tus upload is registered.
- [Get a media upload](https://www.dropfans.io/developers/reference/get-media-upload.md): GET /api/external/v1/media/uploads/{id} — The session's status: which parts arrived, the vault item once completed, and its moderation status.
- [Create a sellable drop from vault items](https://www.dropfans.io/developers/reference/create-drop.md): POST /api/external/v1/drops — Packages up to 10 vault items into a drop and returns a checkout URL.
- [List the creator’s drops](https://www.dropfans.io/developers/reference/list-drops.md): GET /api/external/v1/drops — Every drop on the account, newest first, with price, who can buy it, moderation status and checkout URL — including drops made in the dashboard.
- [Read back a drop](https://www.dropfans.io/developers/reference/get-drop.md): GET /api/external/v1/drops/{id} — One drop you created: price, moderation status (overall and per media item), checkout URL, whether previews are attached, and a sales summary.
- [Edit a drop](https://www.dropfans.io/developers/reference/update-drop.md): PATCH /api/external/v1/drops/{id} — Changes a drop's name, description, price or who can buy it — the same edit the dashboard allows. Send only what changes; `null` clears name or description.
- [Delete a drop nobody has bought](https://www.dropfans.io/developers/reference/delete-drop.md): DELETE /api/external/v1/drops/{id} — Deletes a drop that has no orders — not even an unfinished checkout. Once anyone has an order on it, buyers' access depends on it and the call returns `409 has_orders`.
- [Attach baked blur previews to a drop](https://www.dropfans.io/developers/reference/attach-drop-previews.md): POST /api/external/v1/drops/{id}/previews — Uploads pre-blurred ("baked") JPEG teasers for a drop's media, so the checkout page shows the exact same blur your app showed the buyer elsewhere.
- [Check which drops sold (batch)](https://www.dropfans.io/developers/reference/check-drop-status.md): POST /api/external/v1/drops/check-status — Sale info for a batch of product ids — the polling half of sale tracking.
- [List paid orders (per-fan references)](https://www.dropfans.io/developers/reference/list-orders.md): GET /api/external/v1/orders — Paid drop orders of the key's account, newest first — the polling twin of the [drop.paid webhook](/developers/webhooks/overview).
- [Publish a post to the For You feed](https://www.dropfans.io/developers/reference/create-post.md): POST /api/external/v1/posts — Rate limit: 5 posts per creator per rolling 24 hours. Bursts are fine — only the daily volume is capped. Exceeding it returns 429 with a Retry-After header.
- [List your posts and their moderation status](https://www.dropfans.io/developers/reference/list-posts.md): GET /api/external/v1/posts — Your posts, newest first, plus the current posting limits — read `limits` from the response rather than hardcoding numbers.
- [Check one post’s moderation status](https://www.dropfans.io/developers/reference/get-post.md): GET /api/external/v1/posts/{id} — One post, as a **bare object** (not wrapped). The polling endpoint after a PENDING create: check `status` and `live`.
- [Delete a post (or cancel a scheduled one)](https://www.dropfans.io/developers/reference/delete-post.md): DELETE /api/external/v1/posts/{id} — Hard-deletes one of your posts. Deleting a scheduled post before it goes live cancels it.
- [Earnings stats, chart and recent transactions](https://www.dropfans.io/developers/reference/get-earnings.md): GET /api/external/v1/earnings — The same revenue the creator sees on their own dashboard: drop sales + tips + subscription payments, refunds and chargebacks excluded, bucketed by day in the caller's timezone.
- [Earnings summary: totals, sources and a day / week series](https://www.dropfans.io/developers/reference/get-earnings-summary.md): GET /api/external/v1/earnings/summary — Totals for all time, this month and your window, a breakdown by source (drop, tip, subscription) and a zero-filled day or week series, in integer cents.
- [Full transaction ledger (paginated, net per transaction)](https://www.dropfans.io/developers/reference/list-earnings-transactions.md): GET /api/external/v1/earnings/transactions — Every drop sale, tip and subscription payment of the key's account, newest first, with net, gross, platform fee and VAT per transaction. No cap — follow `nextCursor` until it is null.
- [List paid tips (per-fan references)](https://www.dropfans.io/developers/reference/list-tips.md): GET /api/external/v1/tips — Paid tips of the key's account, newest first — the polling twin of the [tip.paid webhook](/developers/webhooks/overview).
- [The creator’s profile, tip and subscribe links](https://www.dropfans.io/developers/reference/get-links.md): GET /api/external/v1/links — The creator's shareable links in one call. Never build Dropfans URLs by hand.
- [Create a link for a drop, a tip, a subscription or the profile](https://www.dropfans.io/developers/reference/create-link.md): POST /api/external/v1/links — Creates one link id. The link is `https://www.dropfans.io/buy/{id}` (web) and `https://t.me/<bot>/app?startapp={id}` (Telegram), with no parameters. The drop, the tip amount and your `externalRef` are stored with the id.
- [Read the Telegram notification status](https://www.dropfans.io/developers/reference/get-notifications.md): GET /api/external/v1/notifications — Where the creator's sale notifications currently go: their saved handle, whether a personal chat is connected, and whether a group/channel is connected.
- [Update Telegram notification settings](https://www.dropfans.io/developers/reference/update-notifications.md): PUT /api/external/v1/notifications — An action-dispatch endpoint — the `action` field picks one of three operations:
- [Register the creator’s personal notification chat](https://www.dropfans.io/developers/reference/register-telegram-chat.md): POST /api/external/v1/register-telegram-chat — Stores a Telegram chat id as the creator's **personal** notification target — the DM their sale notifications go to.
- [Create a creator account (sign-up from your page)](https://www.dropfans.io/developers/reference/create-account.md): POST /api/external/v1/accounts — Creates a creator (or agency) account from your own sign-up page and returns the ID-check link to redirect the creator to.
- [List accounts you created](https://www.dropfans.io/developers/reference/list-accounts.md): GET /api/external/v1/accounts — Accounts your app created through create-account, newest first, with their current status.
- [Get an account you created](https://www.dropfans.io/developers/reference/get-account.md): GET /api/external/v1/accounts/{id} — Status of one account your app created — `pending_kyc` until the ID check is approved, then `active`.
- [Get a fresh ID-check link](https://www.dropfans.io/developers/reference/create-kyc-session.md): POST /api/external/v1/accounts/{id}/kyc-session — The ID-check link for an account you created — when the first one expired, the creator closed it, or the check was declined and they may try again.
- [Get your webhook endpoint](https://www.dropfans.io/developers/reference/get-webhook.md): GET /api/external/v1/webhooks — Your app’s webhook endpoint, its events and the last 20 deliveries (with status codes and errors) — the first place to look when an event seems missing.
- [Set your webhook endpoint](https://www.dropfans.io/developers/reference/set-webhook.md): PUT /api/external/v1/webhooks — Sets the https endpoint that receives your app’s events. The first call also creates the signing secret and returns it **once** as `secret`. Store it; later calls don’t return it (use rotate-webhook-secret).
- [Remove your webhook endpoint](https://www.dropfans.io/developers/reference/delete-webhook.md): DELETE /api/external/v1/webhooks — Stops deliveries. Events still waiting for a retry are dropped. Poll [GET /api/external/v1/orders](/developers/reference/list-orders) meanwhile.
- [Rotate the webhook signing secret](https://www.dropfans.io/developers/reference/rotate-webhook-secret.md): POST /api/external/v1/webhooks/rotate-secret — Issues a new signing secret and returns it once. Every delivery from now on, including retries, is signed with it. Accept both secrets for a few minutes while you deploy.
- [Send a test event](https://www.dropfans.io/developers/reference/test-webhook.md): POST /api/external/v1/webhooks/test — Sends a signed `ping` event to your endpoint and reports what it answered — use it to check your signature verification.
- [Payout balance, eligibility and status](https://www.dropfans.io/developers/reference/get-payout-summary.md): GET /api/external/v1/payouts/summary — Everything a "Pay out" button needs in one call: balances, the minimum, the payout method and whether a payout request would be accepted right now.
- [Payout history (paginated)](https://www.dropfans.io/developers/reference/list-payouts.md): GET /api/external/v1/payouts — The account's payout history, newest first — the same rows as the creator's Payouts page, in integer cents.
- [One payout or payout request](https://www.dropfans.io/developers/reference/get-payout.md): GET /api/external/v1/payouts/{id} — One row of the history by id — a payout, a manual payout or a payout request — in any status, including failed attempts, fulfilled requests and reversal rows.
- [Payout methods (masked)](https://www.dropfans.io/developers/reference/list-payout-methods.md): GET /api/external/v1/payouts/methods — The account's payout methods, default first, with every destination masked.
- [Add a Paxum payout method](https://www.dropfans.io/developers/reference/create-payout-method.md): POST /api/external/v1/payouts/methods — Add a Paxum account as a payout method — what "Add Paxum" does in the dashboard, with a stricter e-mail check.
- [Change a payout method](https://www.dropfans.io/developers/reference/update-payout-method.md): PATCH /api/external/v1/payouts/methods/{id} — Rename a payout method, make it the default (or stop using it as the default), or point a Paxum method at another Paxum e-mail.
- [Remove a payout method](https://www.dropfans.io/developers/reference/delete-payout-method.md): DELETE /api/external/v1/payouts/methods/{id} — Remove a payout method — refused with 409 `method_in_use` while a payout to it is still pending or processing.
- [MassPay payout profile](https://www.dropfans.io/developers/reference/get-masspay-profile.md): GET /api/external/v1/payouts/masspay/profile — The MassPay payout profile behind the payout wallet, read live from MassPay, with the required fields it still lacks in `missingFields`.
- [Set up the MassPay wallet](https://www.dropfans.io/developers/reference/setup-masspay-wallet.md): POST /api/external/v1/payouts/masspay/profile — Set up the account's MassPay payout wallet from the same profile the dashboard's setup form collects, and make it the default payout method.
- [MassPay wallet activation](https://www.dropfans.io/developers/reference/get-masspay-activation.md): GET /api/external/v1/payouts/masspay/activation — Whether the payee has activated the MassPay wallet and, if not, a fresh `activationUrl` to send them to.
- [Request a payout](https://www.dropfans.io/developers/reference/create-payout-request.md): POST /api/external/v1/payouts/requests — Request a payout of the account's **full** available balance — exactly what "Pay out funds" does in the dashboard.
- [Cancel a payout request](https://www.dropfans.io/developers/reference/cancel-payout-request.md): POST /api/external/v1/payouts/requests/{id}/cancel — Cancel one of the account's payout requests while it is still `requested`.
- [Get your app](https://www.dropfans.io/developers/reference/get-crm-app.md): GET /api/external/v1/crm/app — Your app as we know it: name, logo, status, commission terms and which API categories are switched on. Always the app the key is bound to.
- [Dashboard stats](https://www.dropfans.io/developers/reference/get-crm-stats.md): GET /api/external/v1/crm/stats — Your integration dashboard’s Dashboard tab as data: revenue, booked commission, sales and new accounts, as totals plus zero-filled hour, day, week or month buckets.
- [List sales through your app](https://www.dropfans.io/developers/reference/list-crm-transactions.md): GET /api/external/v1/crm/transactions — Your integration dashboard’s Transactions tab: every sale through your app’s links across all your accounts, newest first, with the commission booked on each.
- [List your connected accounts](https://www.dropfans.io/developers/reference/list-crm-accounts.md): GET /api/external/v1/crm/accounts — Your integration dashboard’s Accounts tab: every account your app has generated links for, with its all-time sales through your links and the commission booked on them.

## Resources

- [Changelog](https://www.dropfans.io/developers/changelog.md): Dated, additive changes to the API and these docs.
- [API terms & acceptable use](https://www.dropfans.io/developers/api-terms.md): What you may and may not do with a creator’s API key.

## Apply

- [Apply for API access](https://www.dropfans.io/developers/apply): Building an app for other people's creators? Apply here (requires a Dropfans login); approved apps appear in every creator's key picker.

## OpenAPI Specs

- [OpenAPI 3.1 spec](https://www.dropfans.io/developers/openapi.json): Every operation, schema, error body and code sample, machine-readable.

## Optional

- [Complete documentation in one file](https://www.dropfans.io/developers/llms-full.txt): Every page of these docs concatenated — ingest this for full context.
- [Dropfans site guide](https://www.dropfans.io/llms.txt): The wider Dropfans platform in one file.