Connect a Photo Booth to Brunchie

A photo-booth vendor's guide to sending every shot straight into the couple's live Brunchie album. dslrBooth and LumaBooth connect with a single copy-paste link — no separate app, no QR-to-Google-Photos.

Connect your photo booth to the couple's Brunchie album

What this does. Your booth (dslrBooth, LumaBooth, or anything that can call 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.

Using dslrBooth or LumaBooth (Windows)? Their built-in Triggers can only call a plain web address — they can't send a token in a separate field. Brunchie handles that with a single all-in-one link. See dslrBooth / LumaBooth — the one-link setup below.


1. Get your connection link from the host

The host sets this up in seconds. In their hangout they open Tools → Connect a booth, where they'll see two ways to connect — they hand you whichever your booth needs:

Connect a booth setup modal on a phone — same three link fields in the fullscreen scrollable modal, including the all-in-one link with key that dslrBooth and LumaBooth users paste as a single trigger URL. Captured at 390x844 mobile. Used by guides/connect-a-photo-booth.md.

  • Booth connection link with key — an all-in-one link with the event key already baked into the path, e.g. https://brunchie.app/api/v1/webhooks/lumabooth/summer-wedding-a1b2c3d4/YOUR_EVENT_KEY. (The key sits in the path, not a ?api_token= — dslrBooth adds its own ?… to the end and only does that when the link has no query string of its own.) This is the one for dslrBooth / LumaBooth — there's no separate token to type anywhere.
  • Booth connection link plus a separate hangout key — for booths that have their own token/header field. You paste the link as the webhook URL and the key wherever your software asks for a token.

Either way, just paste the whole link the host gives you — the event_id is the event's name-based address, not a number, and you never build the URL yourself.

About the key. It's a secret that authenticates your uploads, and it rotates: valid for 7 days, then renews on its own. On the event day, ask the host for a fresh link/key from that same screen. If the host taps Rotate, the old one stops working immediately — so grab the current one close to showtime. Keep it 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.


dslrBooth / LumaBooth — the one-link setup

Connect a booth setup modal — the three link fields a vendor pastes into their booth software: the 7-day hangout key, the plain connection link, and the all-in-one link with the key already baked in (the one dslrBooth and LumaBooth users paste as a single trigger URL). Captured at 1280x900 desktop. Used by guides/connect-a-photo-booth.md.

dslrBooth (and LumaBooth for Windows) fire captures from Settings → General → Triggers, which can only call a plain web address — they can't add a header or attach a token field. That's exactly what the Booth connection link with key is for: the key lives inside the link, so connecting is one paste.

There are two switches, in two different settings screens — both have to be on:

  1. From the host, get the Booth connection link with key (Tools → Connect a booth).
  2. Turn on cloud upload (fotoShare) in dslrBooth's Share / fotoShare settings for photos, GIFs, and videos — including Upload original / Enhanced sharing. The booth sends Brunchie a link to the photo, so the photo has to reach fotoShare first. If cloud upload is off, the trigger fires with no photo and nothing posts.
  3. Open Settings → General → Triggers. This screen just has an Application box and a URL box — there's no event picker to choose. Paste the Booth connection link with key into the URL box. Your key is already in it — there's no separate token to enter.
  4. Take a real capture — a full session, so the fotoShare upload finishes. (The link only exists after the upload completes, so the test/preview button won't post — you need an actual photo.) It lands in the couple's Album tab within a few seconds.

That's the whole setup. dslrBooth calls your link on every step of a session and adds its own details automatically — Brunchie only posts on the photo-uploaded step and reads what it needs from there (the fotoShare share link, the capture filename, and the media type). The filename doubles as a safety check so a retried capture can't post twice.

Re-copy the link for each event. The key rotates every 7 days, and rotating regenerates the link. The "Booth connection link with key" on the Connect-a-booth screen always shows the current one — paste a fresh copy into your trigger for each wedding.


2. The upload endpoint (for booths that can POST)

If your booth software can set a header and POST, you can use the plain endpoint with the Booth connection link + the hangout key:

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

Authenticating

Send the event key one of two ways — the header wins if you somehow send both:

Where Value Use it when
X-Api-Token header Your event key Your booth can set request headers (preferred).
?api_token= in the URL Your event key Your booth can only call a plain URL — dslrBooth / LumaBooth Triggers. This is what the all-in-one link uses.

Form fields

Field Required What it is Example
param1 The guest's QR link (if your booth scans one), or leave it off 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 The media type hint 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). dslrBooth fills param1/param2/param3 for you automatically when it calls the link.

Developers: there's a fuller API with cleaner field names (media, photos[], qr, media_type, visibility, client_id) and direct file upload — no third-party photo host required. See the Photo booth uploads developer guide.


3. Examples

A photo from a floor booth (no guest QR), authenticating with the header:

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

The same upload from a booth that can only call a URL — key in the path, which is what the all-in-one link does (dslrBooth appends the ?event_type=&param2=… part itself):

curl "https://brunchie.app/api/v1/webhooks/lumabooth/summer-wedding-a1b2c3d4/YOUR_EVENT_KEY?event_type=file_upload&param2=https://fotoshare.co/i/abc123&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 link/key from Tools → Connect a booth (for dslrBooth/LumaBooth, re-copy the whole "Booth connection link with key"). An old key never silently keeps working.
  • dslrBooth/LumaBooth: nothing posts at all — two usual causes. (1) fotoShare cloud upload is off, so the trigger fires with no photo link — turn it on (incl. Upload original / Enhanced sharing) in dslrBooth's Share settings. (2) You only tried the test button or opened the link in a browser — the photo-uploaded step (the one that carries the picture) only fires after a real capture finishes uploading, so run a full session.
  • Post appears but no image — your param2/audio_url has to be a public URL Brunchie can fetch. For dslrBooth/LumaBooth, that means cloud upload (fotoShare) must be on. 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 booth and sends you the connection link (the "with key" one for dslrBooth/LumaBooth).
  2. In your booth software, paste the link where it asks for a webhook URL or trigger address. For dslrBooth/LumaBooth that's the URL box under Settings → General → Triggers — no separate token to enter.
  3. Turn on fotoShare cloud upload (incl. Upload original) for dslrBooth/LumaBooth, and set the booth to send photos, videos, and audio.
  4. Take a real capture (a full session, so the upload finishes) — 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

I use dslrBooth — there's no place to enter a token. How do I connect?
You don't enter a token. dslrBooth's Triggers can only call a plain web address, so Brunchie gives the host an all-in-one link with the key already baked in. Paste that one link as your trigger URL and you're connected — see the dslrBooth / LumaBooth section below.
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, GIFs, 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 link or 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 the host hands you, pasted into your booth software's 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