Developers

Fablesh Technical Documentation.

Architecture, authentication, storage, AI production, commerce events and the public API in one maintained technical surface.

Platform architecture

Cloudflare-first web products, protected production services and shared identity.

Authentication & access

Central authentication through auth.fablesh.com, return URLs, sessions and role-based access.

Media & storage

Shared Media Library and Brand Kits backed by separated R2 image, audio and video storage.

AI production

Model routing, explicit price acceptance, provider cost plus Fablesh margin and generation persistence.

Credits & billing

Stripe credit packs, idempotent fulfillment, balance ledgers and usage debits.

Webhooks

Signed Stripe events, replay protection, retry handling and operational diagnostics.

Radio & streaming

Azuracast metadata, HLS playback, station templates and play-history refresh.

API reference

OpenAPI endpoints

Authenticate with Authorization: Bearer cm_live_…. API keys remain restricted to authorised accounts.

Base URL

https://fablesh.com

Authentication

Authorization: Bearer cm_live_…

Available scopes

Each endpoint requires a specific scope. The key’s scopes determine what it can do.

  • read:catalog — Read your submissions and albums via v1
  • write:submissions — Create and update submissions
  • write:albums — Create albums/releases
  • read:audio:web — Fetch signed URL for web transcoding
  • read:audio:master — Fetch signed URL for master file (service only)
  • read:stats — Read playback stats
  • admin:keys — Manage API keys (service only)

User keys can only have: read:catalog, write:submissions, write:albums, read:audio:web, read:stats. Other scopes are reserved for service keys.

Loading documentation…