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-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.