Skip to content

// support, community and events

Via API

Luma email verification with pingutil

Popular Luma events get guests registering with throwaway addresses, which eats capacity and leaves hosts approving people who will never show. A guest.registered webhook sends every registration to your endpoint, pingutil verifies the address, and for events that require approval your code declines clear throwaways through the Update Guest Status endpoint while leaving the rest for the host.

Where it connects: Luma webhook guest.registered, then the Luma API Update Guest Status endpoint (POST /v1/events/guests/update-status)

What goes wrong without it

  • We require approval for our dinners and spend an evening clicking through registrations, half of them on temp-mail domains.
  • Capacity says full, the room is half empty, and the waitlist never moved.
  • Event updates bounce because guests typed their email wrong when they registered on mobile.

What you can do with Luma and pingutil

  • Auto-decline disposable registrations

    For events with approval on, a guest whose address is on a disposable domain is moved to declined with send_email set to false, so the host only reviews plausible guests.

  • Keep the waitlist honest

    Declining throwaway registrations frees capacity, so real guests on the waitlist get a spot instead of a placeholder account.

  • Flag typos for the host

    An invalid result with a did_you_mean suggestion goes to the host (Slack, a sheet, an email) so they can reach the guest before the event updates go out.

Set it up

  1. 1

    Create a pingutil API key (PINGUTIL_KEY) and a Luma API key (LUMA_API_KEY) from your calendar settings. Luma API access and webhooks need Luma Plus.

  2. 2

    In your Luma calendar settings, add a webhook with your endpoint URL (include a secret query string) and subscribe to guest.registered.

  3. 3

    Deploy the handler below. It checks the secret, answers 200, verifies data.user_email and, when the guest is pending approval and the address is disposable, calls Update Guest Status with status declined.

  4. 4

    Send other flagged results to the host instead of changing the guest.

  5. 5

    Register for a test event with a disposable address and confirm the guest moves to declined.

Express handler for Luma guest.registered
import express from 'express';

const app = express();
app.use(express.json());

async function verify(email: string) {
  try {
    const res = await fetch('https://pingutil.com/v1/verify', {
      method: 'POST',
      headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
      body: JSON.stringify({ email }),
      signal: AbortSignal.timeout(30000),
    });
    return res.ok ? await res.json() : null; // fail open on 429 / 5xx
  } catch {
    return null;
  }
}

app.post('/webhooks/luma', async (req, res) => {
  if (req.query.token !== process.env.LUMA_HOOK_TOKEN) return res.sendStatus(401);
  res.sendStatus(200);

  const { type, data } = req.body;
  if (type !== 'guest.registered' || !data.user_email) return;

  const v = await verify(data.user_email);
  if (!v) return; // pingutil unavailable: the host reviews as usual

  if (v.reason === 'disposable_domain' && data.approval_status === 'pending_approval') {
    await fetch('https://public-api.luma.com/v1/events/guests/update-status', {
      method: 'POST',
      headers: { 'x-luma-api-key': process.env.LUMA_API_KEY!, 'content-type': 'application/json' },
      body: JSON.stringify({ event_id: data.event.id, guest_id: data.id, status: 'declined', send_email: false }),
    });
    return;
  }

  if (v.status === 'invalid' || v.status === 'risky') {
    // Tell the host; replace with Slack, email or a sheet
    console.log(JSON.stringify({ event: data.event.id, guest: data.user_name, email: data.user_email, status: v.status, reason: v.reason, did_you_mean: v.did_you_mean }));
  }
});

app.listen(3000);

What to do with each result

pingutil resultAction in Luma
reason: 'disposable_domain' on a pending guestSet the guest to declined with send_email: false.
reason: 'disposable_domain' on an approved guestNotify the host; do not decline automatically once someone has been told they are going.
status: 'invalid' with did_you_meanSend the suggestion to the host so they can contact the guest.
status: 'risky'Leave the guest as is and mention it in the host summary.
status: 'valid' or 'unknown'No change; the host approves as normal.

Limits to plan for

  • Luma API keys and webhooks require Luma Plus, and the API is rate limited (200 requests per minute per calendar key).
  • Luma's webhook reference does not document a signature header, so protect the endpoint with a secret in the URL.
  • Auto-decline only makes sense on events that require approval. On open events the guest is already going, so flag instead of declining.

Luma documentation

Luma is a trademark of its owner. This integration uses Luma's documented extension points; it is not an official Luma app.

Common questions

Will the declined guest get an email?
Not with send_email set to false, as in the snippet. Set it to true if you want Luma to tell them.
Does guest.registered fire again if someone re-registers?
Yes, Luma documents that it fires on re-registration after a cancellation. pingutil caches results, but each call still counts toward your daily verification budget.

Stop bad addresses in Luma today

Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Luma setup will receive.