Skip to content

// support, community and events

Via API

Eventbrite email verification with pingutil

Free and low-cost Eventbrite events attract registrations from throwaway addresses and typos, so your headcount is inflated and reminder emails bounce. An order.placed webhook gives you the order URL, your code fetches the order with its attendees, pingutil verifies each address, and you get a clean list of who you can actually reach before you plan catering or send the join details.

Where it connects: Eventbrite webhook with the order.placed action, then the Orders API (expand=attendees)

What goes wrong without it

  • Registrations for our free meetup looked great, the room was half empty, and a chunk of the list was mailinator addresses.
  • Reminder emails bounce because people rushed through checkout and typed their email wrong.
  • Someone grabbed a stack of free tickets with different temp-mail addresses and our capacity filled up.

What you can do with Eventbrite and pingutil

  • Real headcount before you order catering

    Store each order with its verification status. Count only valid and risky addresses when you plan capacity, and treat disposable registrations as likely no-shows.

  • Contact attendees whose email bounced

    An invalid result with a did_you_mean suggestion goes onto a follow-up list, so the organizer can reach the attendee through the suggested address or at check-in.

  • Spot ticket hoarding on free events

    Several disposable registrations in a short window point to one person grabbing capacity. Flag them for the organizer to review and cancel in the Eventbrite dashboard.

Set it up

  1. 1

    Create a pingutil API key (PINGUTIL_KEY) and an Eventbrite private token (EVENTBRITE_TOKEN).

  2. 2

    In Eventbrite, go to Account Settings, Developer Links, Webhooks, and add a webhook with your endpoint URL (include a secret query string) and the order.placed action.

  3. 3

    Deploy the handler below. It checks the secret, answers 200, fetches the order from the api_url in the payload with expand=attendees, and verifies the buyer and attendee addresses in one batch call.

  4. 4

    Results are saved to your own store (a database, a sheet or a Slack message to the organizer). Eventbrite has no field on the order to write the result back to.

  5. 5

    Place a test order on a draft event and confirm the result lands where you expect.

Express handler for Eventbrite order.placed
import express from 'express';

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

async function verifyBatch(emails: string[]) {
  try {
    const res = await fetch('https://pingutil.com/v1/verify/batch', {
      method: 'POST',
      headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
      body: JSON.stringify({ emails: emails.slice(0, 50) }), // batch takes up to 50 addresses
      signal: AbortSignal.timeout(60000),
    });
    return res.ok ? (await res.json()).results : null; // fail open on 429 / 5xx
  } catch {
    return null;
  }
}

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

  const apiUrl: string = req.body.api_url ?? '';
  if (!apiUrl.startsWith('https://www.eventbriteapi.com/v3/orders/')) return; // only follow Eventbrite order URLs

  const order = await fetch(apiUrl + '?expand=attendees', {
    headers: { authorization: 'Bearer ' + process.env.EVENTBRITE_TOKEN },
  }).then((r) => r.json());

  const emails = new Set<string>([order.email]);
  for (const a of order.attendees ?? []) if (a.profile?.email) emails.add(a.profile.email);

  const results = await verifyBatch([...emails].filter(Boolean));
  if (!results) return;

  for (const r of results) {
    // Replace with your own store: a database row, a Google Sheet, a Slack message to the organizer
    console.log(JSON.stringify({
      event_id: order.event_id,
      order_id: order.id,
      email: r.input,
      status: r.status,
      reason: r.reason,
      did_you_mean: r.did_you_mean,
    }));
  }
});

app.listen(3000);

What to do with each result

pingutil resultAction in Eventbrite
status: 'valid'Count the registration in your expected headcount.
reason: 'disposable_domain'Mark as a likely no-show; if several arrive from one buyer, flag for the organizer to cancel in the dashboard.
status: 'invalid' with did_you_meanAdd to a follow-up list with the suggested address so the attendee still gets event details.
status: 'risky' (accept_all)Count the registration but expect some reminder bounces from catch-all company domains.
status: 'unknown'Count it; the mail server did not answer, which says nothing about the attendee.

Limits to plan for

  • Eventbrite gives you no documented order field for the result, so the outcome lives in your own system and any cancellation is done by the organizer.
  • Developers have reported missed order.placed deliveries; for important events, reconcile with a periodic pull of the event's orders.
  • The batch endpoint takes up to 50 addresses per call and every address counts toward the 300 verifications per day (3,000 a month) account default, so very large events need the dashboard CSV upload or a budget plan. Those are Free plan limits; Enterprise has custom limits.

Eventbrite documentation

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

Common questions

Can pingutil stop the registration at checkout?
No. Eventbrite checkout runs on Eventbrite, and the webhook fires after the order is placed. You get the result in seconds and decide what to do with the registration.
Why fetch the order instead of trusting the webhook body?
The webhook only carries an api_url. Fetching it with your own token gives you the real order and attendees and means a forged request cannot inject data.

Stop bad addresses in Eventbrite 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 Eventbrite setup will receive.