For developers
Built for the teams who ship it
A REST API and client SDKs on a platform you deploy in your own environment. Engineering integrates the live data layer once; the engagement surfaces on top are in design preview, and we label them that way.
An API-first platform
A clean resource model (Applications → Profiles → Programs, with Widget and Reward surfaces in preview) that you integrate once.
REST API (Live)
The live data layer is programmable over a REST API with OAuth 2.0: profiles, identity, events, programs, and measurement. The client secret stays server-side; profile tokens scope a single fan.
Identity & data model (Live)
Map your existing user, CMS, commerce, or stats IDs one-to-one with custom identifiers; queryable attributes handle one-to-many. No parallel database to maintain.
Client SDKs (surfaces in Preview)
SDKs for iOS, Android, and Web. The data and identity calls are live; the interactive widget, rewards, and leaderboard surfaces they will render are in design preview.
Fits the stack you already run
Connect Sfere to your identity, content, and data systems without rebuilding them. Engineering owns the integration; the producer surface owns the day-to-day.
- OAuth 2.0 Bearer auth: the client secret stays server-side, and profile tokens scope a single fan.
- Custom IDs map your CMS, commerce, EPG, or stats systems one-to-one; queryable attributes handle one-to-many.
- Programs emit start/stop status events your integrations can subscribe to.
- Spoiler-safe playback sync (HLS Program-Date-Time) is designed into the client SDK. (Design preview.)
- Live today: the identity, profile, program, and data APIs. In design preview: the interactive widget, rewards, and leaderboard surfaces.
Evaluate it like an engineer
There's no self-serve sandbox today, and we won't pretend otherwise. Evaluation is a guided, technical walkthrough on your use case, with the reference material to go deep.
- The full API reference is shared under guided evaluation today; a public docs portal is on the roadmap, not promised for a date.
- Evaluation is hands-on: walk the API surface, the deployment model, and the identity rules with our engineers.
- Browse the connector directory to see what plugs in without custom work.
- Read the architecture overview for how collect, resolve, activate, and prove fit together.
How the system fits together
Collect, resolve, store, activate, and prove, as one vendor-generic architecture.
Where fans become players.
See how Sfere turns your live audience into active, returning, monetizable fans. Book a walkthrough with our team.