Connect a Photo Booth to Brunchie

A photo-booth vendor's guide to sending every shot straight into the couple's live Brunchie album over the API — no QR-to-Google-Photos, no separate app.

Connect your photo booth to the couple's Brunchie album

What this does. Your booth (LumaBooth, dslrBooth, or anything that can POST a webhook) sends each shot straight into the couple's Brunchie hangout — the same live album their guests are already posting to from the reception.

Why it beats the usual handoff. No QR-code-to-a-shared-Google-album. No "we'll email you the gallery link next week." No separate app for anyone to install. The photos land in the album as they're taken, attributed to the right people, in the one place the couple already opens.

So what. By the time the night's over, the couple has a single assembled album — your booth shots, guest phone photos, and voice messages all in one feed — and your booth looks seamless instead of like a separate silo they have to chase down later.


1. Get your connection link + event key

The host sets this up in seconds and hands you two things. In their hangout they open Tools → Connect a photo booth and copy:

  • Connection link — the full upload URL, already pointing at their event, e.g. https://brunchie.app/api/v1/webhooks/lumabooth?event_id=summer-wedding-a1b2c3d4. The event_id is the event's name-based address, not a number — just paste the whole link, you don't build it yourself.
  • Event key — the secret that authenticates your uploads. It rotates: it's valid for 7 days, then renews on its own. On the event day, ask the host for a fresh key from that same screen. If the host taps Rotate, the old key stops working immediately — so grab the current one close to showtime.

Keep the event key private. Anyone who has it can post to the couple's album, so treat it like the venue's wifi password — for your booth only.


2. The upload endpoint

The connection link the host gives you already includes the ?event_id=…, so you POST straight to it:

POST https://brunchie.app/api/v1/webhooks/lumabooth?event_id=<event-name>

Header

Header Value
X-Api-Token Your event key (from the host — the 7-day rotating one)

Form fields

Field Required What it is Example
param1 Yes The guest's QR link (if your booth scans one) or anonymous for a floor booth https://brunchie.app/qr/abc123def456
param2 If no audio_url A public URL to the photo or video (images under 10 MB, video under 200 MB) https://yourbooth.example/photo123.jpg
param3 Yes The media type image, video, boomerang, or audio
audio_url If no param2 A public URL to a voice message (audio under 10 MB, up to 60 seconds) https://yourbooth.example/voice123.mp3

Send param2, audio_url, or both (a photo with a voice message rides on one post).


3. Examples

A photo from a floor booth (no guest QR):

curl -X POST "https://brunchie.app/api/v1/webhooks/lumabooth?event_id=summer-wedding-a1b2c3d4" \
  -H "X-Api-Token: YOUR_EVENT_KEY" \
  -d "param1=anonymous" \
  -d "param2=https://yourbooth.example/photo123.jpg" \
  -d "param3=image"

A photo credited to a guest whose QR you scanned:

curl -X POST "https://brunchie.app/api/v1/webhooks/lumabooth?event_id=summer-wedding-a1b2c3d4" \
  -H "X-Api-Token: YOUR_EVENT_KEY" \
  -d "param1=https://brunchie.app/qr/abc123def456" \
  -d "param2=https://yourbooth.example/photo123.jpg" \
  -d "param3=image"

A success returns 200/201; the shot appears in the couple's Album tab within a few seconds.


4. Who each shot is posted by

You don't have to scan anyone — attribution just works:

  • No QR (the common floor-booth case) → the shot lands in the shared album, posted by Brunchie's album bot, Benny Brunch. Nothing is dropped.
  • A guest's personal QR rides along → the shot is credited to that guest, exactly as if they'd posted it themselves.

Either way the photo is visible to everyone at the wedding in the same feed.


5. If something's not landing

  • 401 Unauthorized — the event key is wrong, expired (7-day), or was rotated. Ask the host for the current key from Tools → Connect a photo booth. (An old key never silently keeps working.)
  • Post appears but no image — your param2/audio_url has to be a public URL Brunchie can fetch. If your CDN link is private or expired, the post is created without the media; re-send once the URL is reachable.
  • Wrong event — double-check you're posting to the connection link for this couple's hangout (the event_id in the URL identifies it).
  • Video still processing — videos transcode in the background and appear within a minute.

Setup, start to finish

  1. Host opens Tools → Connect a photo booth and sends you the connection link + a fresh event key.
  2. In your booth software, paste the connection link as the webhook URL and the event key as the token/X-Api-Token.
  3. Set it to send photos, videos, and audio.
  4. Take a test shot — it shows up in the couple's Album tab within a few seconds.

That's it. Every shot for the rest of the night flows straight into the album the couple already loves.

Common questions

Do guests need to scan a QR for every shot?
No. A floor booth usually scans nobody — those shots still land in the album, posted by Brunchie's album bot, Benny Brunch. If a guest's personal QR rides along, the shot is credited to that guest instead.
Where do my uploads show up?
In the hangout's Album tab — the same shared feed the couple and their guests already use. Photos, videos, boomerangs, and voice messages all land there as they're taken.
What if my event key stops working mid-event?
The key rotates every 7 days, and the host can revoke it anytime with Rotate. If uploads start returning 401, ask the host to grab you a fresh key from Tools → Connect a booth.
Is there a separate vendor account or app to install?
No. There's no Brunchie account or app for you to set up — just the connection link and event key the host hands you, pasted into your booth software's webhook settings.

Try Brunchie free

Brunchie replaces the spreadsheet, the group chat, and the half-finished invite list. Free forever for the people we built it for.

Get started