How to Integrate Lovable with Eventbrite

Eventbrite's API uses a simple private token (also called an API key) rather than a complex OAuth flow for account-level access. Navigate to www.eventbrite.com, sign in, and go to Account Settings → Developer links → API Keys → Create API Key. Give it a name like 'My Lovable App'. Eventbrite will create an API key with several associated tokens. The one you need is the 'Private Token' — it looks like a long alphanumeric string beginning with a number or letter. This token authenticates all API requests as your Eventbrite account. For applications where end users log in with their own Eventbrite accounts, Eventbrite does offer OAuth2 — but for the most common Lovable use case (building a dashboard for your own events or as an event organizer), the private token is simpler and fully sufficient. Note your organization ID while in the developer portal. The Eventbrite API scopes most resources to an organization — your events, orders, and attendees are all retrieved relative to an organization ID. You can also get it from the API: call https://www.eventbrite.com/api/v3/users/me/ with your token and look for the 'organizations' array in the response. Eventbrite private tokens do not expire unless you revoke them manually or reset them from the developer settings page.

Open your Lovable project, click the '+' icon next to the Preview label to open the Cloud panel, and navigate to the Secrets tab. Add the following secrets: - Name: EVENTBRITE_TOKEN — Value: your Eventbrite private token - Name: EVENTBRITE_ORG_ID — Value: your numeric Eventbrite organization ID These two values are all the Edge Function needs to authenticate and scope all Eventbrite API calls. The private token provides access to all events, orders, and attendee data in your Eventbrite account — treat it with the same care as a database password. If you are building a multi-organizer platform where different users manage their own Eventbrite accounts, you would implement the OAuth2 flow and store each user's access token in Supabase linked to their user ID. For a single-organizer tool (the most common Lovable use case), the private token approach is correct.

Create a Supabase Edge Function that proxies Eventbrite API v3 calls. The Eventbrite API base URL is https://www.eventbrite.com/api/v3/ and all requests include the Authorization: Bearer {token} header. The Edge Function handles five core actions: events (list all events for the organization), event_details (get full details for a single event including ticket classes), orders (list orders for an event with buyer information), attendees (list attendees for an event with check-in status), and checkin (mark an attendee as checked in using their barcode or attendee ID). Eventbrite's API uses pagination with a next page URL token for large result sets. The Edge Function returns both the current page of results and the pagination cursor so your frontend can implement infinite scroll or load-more pagination.

1// supabase/functions/eventbrite-api/index.ts
2const EVENTBRITE_BASE = 'https://www.eventbrite.com/api/v3';
3
4Deno.serve(async (req) => {
5  if (req.method === 'OPTIONS') {
6    return new Response(null, {
7      headers: {
8        'Access-Control-Allow-Origin': '*',
9        'Access-Control-Allow-Methods': 'POST, OPTIONS',
10        'Access-Control-Allow-Headers': 'Content-Type, Authorization',
11      },
12    });
13  }
14
15  const token = Deno.env.get('EVENTBRITE_TOKEN');
16  const orgId = Deno.env.get('EVENTBRITE_ORG_ID');
17
18  if (!token || !orgId) {
19    return new Response(JSON.stringify({ error: 'Eventbrite credentials not configured' }), {
20      status: 500,
21      headers: { 'Content-Type': 'application/json', 'Access-Control-Allow-Origin': '*' },
22    });
23  }
24
25  const authHeaders = {
26    'Authorization': `Bearer ${token}`,
27    'Content-Type': 'application/json',
28  };
29
30  const { action, params } = await req.json();
31  let url: string;
32  let fetchOptions: RequestInit = { method: 'GET', headers: authHeaders };
33
34  if (action === 'events') {
35    url = `${EVENTBRITE_BASE}/organizations/${orgId}/events/?expand=ticket_availability,ticket_classes&status=live,draft,ended&page_size=50`;
36  } else if (action === 'event_details') {
37    url = `${EVENTBRITE_BASE}/events/${params.event_id}/?expand=ticket_classes,venue`;
38  } else if (action === 'orders') {
39    url = `${EVENTBRITE_BASE}/events/${params.event_id}/orders/?expand=attendees&page_size=100`;
40  } else if (action === 'attendees') {
41    url = `${EVENTBRITE_BASE}/events/${params.event_id}/attendees/?page_size=100`;
42    if (params.page_token) url += `&continuation=${params.page_token}`;
43  } else if (action === 'checkin') {
44    url = `${EVENTBRITE_BASE}/events/${params.event_id}/attendees/${params.attendee_id}/check_ins/`;
45    fetchOptions = { method: 'POST', headers: authHeaders, body: JSON.stringify({}) };
46  } else {
47    return new Response(JSON.stringify({ error: 'Invalid action' }), {
48      status: 400,
49      headers: { 'Content-Type': 'application/json', 'Access-Control-Allow-Origin': '*' },
50    });
51  }
52
53  const response = await fetch(url, fetchOptions);
54  const data = await response.json();
55
56  return new Response(JSON.stringify(data), {
57    status: response.ok ? 200 : response.status,
58    headers: { 'Content-Type': 'application/json', 'Access-Control-Allow-Origin': '*' },
59  });
60});

Use Lovable's chat to create the event management interface. For the sales dashboard, the key metrics are: total capacity, tickets sold per tier, total revenue, refunds issued, and the net attendee count. Eventbrite returns this data via the ticket_availability expand on the events endpoint and through the orders endpoint. For the attendee management view, generate a searchable table showing all registered attendees with their name, email, ticket type, order date, and check-in status. Add a search bar that filters by name or email client-side. Add an export button that generates a CSV of the attendee list using JavaScript's Blob API. For the check-in tool, build a simple input form where venue staff type or scan an attendee barcode. The barcode is visible on each attendee's Eventbrite ticket and is returned by the attendees API endpoint as the barcode field. Look up the attendee by barcode by filtering the local attendees list (cached in Supabase or component state) and then calling the check-in action on the Edge Function. Eventbrite's API also supports creating events and ticket classes programmatically. Prompt Lovable to add an event creation form that calls the events endpoint with a POST body containing event name, start/end time, venue, description, and ticket class definitions. This is useful if you want your Lovable app to be the primary interface for managing Eventbrite events.