Example applications
Composer provides pre-configured example applications to help you get started quickly. These are designed to work with your API keys and can be used to test your checkpoints, while serving as a reference for how the SDKs work together in practice.
Configure repository
Example applications are available on GitHub: https://github.com/spreedly/composer-examples.git — unconfirmed, left as-is, see flag above.
git clone https://github.com/spreedly/composer-examples.gitNavigate to the composer-examples directory and follow the README instructions.
Setup the Node.js backend
- Navigate to server/node-ts
- Configure your .env file per the README
- Run the startup commands per the README
Setup the Next frontend
- Navigate to client/web-next
- Configure your .env file per the README
- Run the startup commands per the README
Experiement with example functionality
Once running, interact with the application to see Composer in action:
- Track users, sessions, and devices — See how Composer tracks users, sessions, and devices (session replay, device fingerprinting, etc.).
- Call a Checkpoint — Enter a checkpoint name from the Composer Dashboard and observe how the application responds.
- Send a Server Event — Send a server event and observe the response.
View developer logs
After sending checkpoints, view logs in the Composer Dashboard under Developer Center > Logs.
Modify checkpoints and test real workflows
Once you've tested an empty workflow, start adding logic to checkpoints. A good starting point is adding an MFA step — see Adding MFA to your Application for more. For a payment-processing example, see Building a transaction processing checkpoint. This demonstrates how multi-step workflows can be built and managed without changing code.
Updated 9 days ago

