Skip to main content
The Fanfare SDK helps you add controlled-access experiences to your application. It gives your application a typed way to start an experience, respond to access requirements, render the consumer’s current state, and send granted consumers to the next step in your flow. This SDK documentation is intentionally contract-first. It explains the public states, actions, callbacks, and customization surfaces you can build against. It does not describe private enforcement logic, abuse-prevention details, or operational details that are not required for integration.

​
Mental model

Fanfare SDK mental model showing a customer application using the SDK to read public journey state and actions from Fanfare. The core concept is a journey. A journey represents one consumer’s progress through one Fanfare experience. Your integration reads the journey state and presents the right UI for that state.

​
Integration paths

All paths use the same journey model. Even if you start with ExperienceWidget, understanding the core journey states will make customization and troubleshooting easier.

​
Packages

Install only the packages your integration needs. React integrations usually install @fanfare-io/fanfare-sdk-core and @fanfare-io/fanfare-sdk-react. Web component integrations use @fanfare-io/fanfare-sdk-solid, which registers the custom element wrapper.

​
First decision

Start with Choose Your Path, then read the Core SDK quickstart. The quickstart introduces the journey contract that every higher-level component uses.