Skip to main content

API Support for Starting a Session with a Selected Preset/Template

Feature Request

Good afternoon LumaBooth team,

I wanted to ask whether it would be possible to add an API command that starts a camera session with a selected preset or template.

Currently, the API allows starting different session types such as Print, GIF, Boomerang, or Video, but there does not seem to be a way to force which preset/template should be used for that specific session.

For our use case, it would be very useful to trigger a session from an external system while also specifying the exact preset/template to apply.

Could this be considered for a future update?

Thank you

Posted by 520051491 ·
2 comments

This request was merged into another request

Comments2

  • Luma Mike

    Team•

    May 19

    Please explain how you would use this.

    • 520051491

      •

      Jun 19

      Hello,

      Sorry for the delay.

      One of the main reasons is to support integrations where another application determines the experience before launching a session.

      Today, an external system can start a Print, GIF, Boomerang, or Video session, but it cannot ensure that the correct preset/template is used. This creates a gap because the external application may already know which experience should be launched based on user choices, purchased options, branding requirements, or workflow logic.

      Another use case is when developers want to create their own custom user experience (landing screen) while still relying on LumaBooth for the capture, processing, and printing workflow. In that scenario, the external application handles the user interface and then launches LumaBooth with the appropriate preset already selected.

      Being able to specify a preset when starting a session would allow external systems to fully control the session configuration rather than only the session type.

      This would make the API much more suitable for automation, third-party integrations, and custom front-end experiences while ensuring the correct preset is selected automatically for each session.

      For example, an additional parameter could be accepted when starting a session, such as:

      http://localhost:1500/api/start?mode=print&template=TemplateA

      or perhaps a template ID/name depending on how presets are internally referenced.

      Thank you for considering it.