📚
Catalog API
Future read-only access to public book metadata, categories, collections and discovery records.
GET /api/read/catalog
Future Read API
API Catalog Foundation
Future Platform APIs
Bwenieve Read APIs prepares the future integration map for catalog, creators, discovery, publishing, reader access and platform status while keeping all current systems static and safe.
✍️
Creator API
Future verified creator profiles, badges, public author records and publishing status visibility.
GET /api/read/creators
Future Public API
🧭
Discovery API
Future endpoints for trending, categories, search, collections and editorial discovery.
GET /api/read/discover
Future Discovery
🚀
Publishing API
Future protected creator publishing workflow after verification, permissions and review systems exist.
POST /api/read/publishing
Future Protected API
🔐
Access API
Future reader-safe access checks that must never bypass payment verification or session protection.
POST /api/read/access
Protected Boundary
📡
Status API
Future operational status and availability reporting for public trust and creator communication.
GET /api/read/status
Future Status
API Governance Principles
Read-Only FirstStart with public metadata APIs before write operations.
Protected AccessAccess APIs must preserve unlock verification and session rules.
No Payment CouplingDeveloper APIs should not alter Daraja or STK flows.
Versioned GrowthFuture APIs should be versioned and documented before release.