Cookbook

Task-oriented recipes for the flows extension developers build most often. Each page focuses on one topic, states the goal, and shows the exact sequence of SDK calls. For the full API surface, see Requests, Events, and Entities.

Conventions

Two rules apply to every snippet in this cookbook:

• Call createExtHelper() once at the top of each page. In the snippets, ext is that instance.
• Keep durable logic (timers, state, coordination) in the EXTENSION_SLOT_BACKGROUND slot. Visual slots can unmount at any time.
• Identifiers prefixed with your (e.g. yourValidate(), <YourSpinner />) are your own code — components and functions you implement, not platform APIs.

Sections

• Payments — charge for actions and react to confirmed payments
• Slot communication & state — keep state in the background slot and sync it to slots
• Activity — reserve and animate the on-screen overlays
• Chat — post messages from the extension and from a chat bot
• Settings — build a settings form and react to changes
• Slot page resolution — decide which page each slot renders
• Storage — persist data without your own infrastructure
• Long-term sessions — durable, shared game state
• Backend — server-side work with extension actions
• Auth — move a guest to a signed-in user
• Monitoring — report business-critical failures