Better public API support

[stridera]

Bobbinry exposes data through an internal API, but there's room to grow a proper public/external API story — stable endpoints, auth, docs, rate limits, and possibly SDKs.

Share what you'd want to build against it (custom dashboards, writing stats, reader bots, export pipelines, analytics, etc.) and what surface area matters most to you.

👍 this post to vote, comment with specifics.

[stridera]

Worth considering write support too, not just read-only endpoints. Some use cases:

• Auto-syncing manuscripts from Scrivener (or other desktop writing apps) via a script that watches the project and pushes chapter changes upstream.
• Letting native desktop writing apps connect directly and treat Bobbinry as a backing store.
• Importers that run locally and stream content in, rather than one-shot uploads.

This would need thought around auth (personal access tokens?), conflict handling when the web editor and a sync script both touch the same chapter, and which entities are writable vs. read-only.

Concern: a write API makes it considerably easier to post generative AI content at scale. Worth thinking through what guardrails (if any) belong at the API layer vs. policy layer before opening this up.