Realtime and push API for channels, presence, and notifications

ChefSphere realtime and push APIs cover channel access, presence, and notification delivery so your app can wake users and sync state without inventing a message bus. This is the connective tissue for social likes, order updates, and plan changes—not a full live streaming product with chat rooms and recordings. If you need create/join streams and session analytics, read the live streaming guide instead of stretching push into a broadcast studio.

Keeping those intents separate prevents architecture mistakes where teams bolt a player onto a notification channel and call it live cooking. It also keeps prepaid planning honest: realtime connect has its own weight band, while live session access sits heavier on the published table. One shared balance still funds both, but your mix should reflect which product surface users actually open every day.

Channel access should be explicit about who may subscribe and what events they are allowed to see, especially when commerce or private household data is involved. Presence helps collaborative surfaces feel alive without polling, while notification delivery covers the offline path when users are not connected. Design deep links and quiet hours as product rules before you spray every like into a push that trains users to disable notifications.

Realtime connect sits above cheap catalog reads on the prepaid token table because maintaining connections and fanout is not free infrastructure. Still, it is typically lighter than AI vision or marketplace checkout, which is why many apps can afford healthy notification volume on Growth packs. Packs start at $29 for 200,000 tokens once early access is granted; unused tokens stay on the balance between campaign spikes.

Pair realtime with social when engagement events should notify, and pair with marketplace when order status must reach buyers without opening the app constantly. Pair with meal planning when household collaborators need timely updates without refreshing a static screen. Early access onboarding is where we align which event classes matter in version one versus noisy nice-to-haves.

Authenticate calls with an X-API-Key in the Firebase-style model and burn prepaid tokens per operation against one ledger across nineteen modules. Request access, describe your notification taxonomy and platforms, and we email you when onboarding opens for your use case.

Docs include illustrative OpenAPI shapes for planning client integration and server fanout patterns without pretending every sample path is a live production contract. Production contracts and environments arrive with access so you integrate against the real surface for channels and notifications. Enterprise from $300 per month exists when dedicated limits or custom weights are required for high fanout workloads.

Ship a small set of high-signal events first: order updates, plan invites, and safety-critical messages beat vanity like spam every time for retention. Measure opt-out rates and support tickets before expanding to every social micro-interaction your feed can emit. Realtime should make the product feel responsive, not make your brand feel needy in the notification shade.

Related guides on live streaming, social feed, and multi-module token billing help you place push correctly in the stack and the prepaid budget. Request early access with rough daily active user estimates and which events are must-have for launch. We will contact you when keys and packs are available.