Changelog

Changes to the API are additive — new fields, new endpoints — and land here with a date. A breaking change would get its own dated entry and advance warning before it happens. Check this page (or its Markdown twin) when something looks new.

2026-10-23 — Referral commission on drops a CRM app creates#

• Drops created with a CRM app’s keys (apps with CRM sign-up enabled) earn the app owner the 5% referral commission on every sale of that drop, with no time limit. On those sales it replaces the creator’s own referrer.

2026-10-23 — Per-fan references on tips#

• Tip links can carry your per-fan reference: ?tip={usd}&m={externalRef} on the web, startapp=tm_{cents}{externalRef}{username} in Telegram ({cents} 0 = the fan picks; there the reference is 1–20 of A-Z a-z 0-9 - with no underscore). GET /links returns tipWithRefTemplate for both.
• New webhook events: tip.paid and tip.refunded, with externalRef and the fan’s message.
• New endpoint: GET /api/external/tips — paid tips with externalRef, message, tipper and status; filter by externalRef or since.

2026-10-17 — Per-fan references, webhooks and creator sign-up#

• Per-fan checkout references: share ONE drop with many fans. Add ?m={externalRef} to the buy link (Telegram: startapp=b_{productId}_{externalRef}); the reference comes back on every paid order. GET /links returns buyWithRefTemplate for both.
• New endpoint: GET /api/external/orders — paid drop orders with externalRef, buyer and status; filter by productId, externalRef or since.
• POST /drops/check-status now also returns orders — every paid order per product (the existing sales map is unchanged).
• Webhooks are live: drop.paid, drop.refunded and account.kyc_updated, HMAC-signed (DropFans-Signature) with retries. Configure with PUT /api/external/webhooks using a key the app owner holds.
• Creator sign-up for approved CRM apps: POST /api/external/accounts creates a creator account with profile, residency, images and subscription price, returns the ID-check link and a key for the account, and credits the referral commission to the app owner.

2026-08-19 — Public launch#

• Apps & approval: third-party integrations can now apply for API access at /developers/apply. Approved apps appear in the key picker under Vault → API Connect.
• Rate limits: every response now carries X-RateLimit-* headers (minute and day windows, per tier). Dropfans-operated integrations are exempt.
• New endpoint: GET /api/external/drops/{id} — read back a drop you created, including per-item moderation status and sales count.
• New endpoint: GET /api/external/links — canonical web and Telegram Mini App links (profile, tip, subscribe, buy) for the creator behind the key.
• Web tip links: /u/<username>?tip=1 opens the tip sheet; ?tip=<usd> opens it prefilled.
• Malformed JSON on PUT /timezone, PUT /notifications and POST /register-telegram-chat now returns 400 {"error":"Invalid JSON body"} instead of an unstructured 500.
• POST /api/external/posts now builds the returned url from the configured app URL instead of a hardcoded host.
• Drops created through the API now carry the correct moderation status at creation — a drop built from approved vault items is born APPROVED and can be attached to a post immediately.
• Full documentation: every endpoint is now documented at /developers, with an OpenAPI 3.1 spec, llms.txt / llms-full.txt editions and a Markdown twin of every page.

Next: API terms & acceptable use or API reference.