Authentication & API keys
Every request carries Authorization: Bearer dpfn_… — a key acts for one account and grants the full surface; agency keys can name a managed account.
Questions? support@dropfans.io
Every request carries Authorization: Bearer dpfn_… — a key acts for one account and grants the full surface; agency keys can name a managed account.
Questions? support@dropfans.io
Every request sends the key in the Authorization header, exactly like this:
Authorization: Bearer dpfn_your_key_hereThe literal Bearer prefix, one space, then the key. Keys always start with dpfn_. Anything else — a missing prefix, a stray newline, an X-Api-Key header — returns 401 { "error": "Unauthorized", "code": "unauthorized" }.
By default a key acts for one account — the one it belongs to — and grants the full surface for it: vault read and write, drops, posts, earnings, balance, profile, links and Telegram notification settings. There are no scopes and no expiry — a key works until it is revoked. Posts and drops created with a key are authored by the account it acts for.
Two exceptions: an agency’s own key can act for any creator or AI persona the agency manages, and your app owner’s own key can act for the accounts your app onboarded — both by calling /api/external/v1/creators/{creatorId}/…. See Acting for a creator.
The creator picks at generation time, and the choice is fixed for the life of the key:
GET /me tells you which kind you hold — see Make your first call.
Creators revoke keys from the same screen they were generated on (Vault → API Connect). A revoked key returns 401 immediately and forever. Handle a 401 by asking the creator to reconnect, never by retrying in a loop.
Next: Apps & approval or Rate limits.