--- title: Eventzilla API Integration on Truto slug: eventzilla category: Event Management canonical: "https://truto.one/integrations/detail/eventzilla/" --- # Eventzilla API Integration on Truto **Category:** Event Management **Status:** Generally available ## MCP-ready AI tools Truto exposes 20 tools for Eventzilla that AI agents can call directly. - **get_single_eventzilla_event_by_id** — Get a single Eventzilla event by id. Returns: id, title, description, currency, start_date, start_time, end_date, end_time, dateid (needed for checkout), time_zone, tickets_sold, tickets_total, status, url, logo_url, venue, categories. Required: id. - **list_all_eventzilla_events** — List events in the Eventzilla account, optionally filtered by status (live, draft, unpublished, completed) or category. Returns event records with id, title, description, currency, start_date, start_time, end_date, end_time, dateid, time_zone, tickets_sold, tickets_total, status, url, venue and categories. Paginate with limit and offset. - **eventzilla_events_togglesales** — Turn ticket sales on or off for an Eventzilla event (publish or unpublish sales). Returns: eventstatus. Required: event_id, status. - **list_all_eventzilla_event_categories** — List the event categories available for the authenticated Eventzilla account. Returns each category as a record with its category name (e.g. Business, Conferences, Networking, Training). - **create_a_eventzilla_event_ticket_type** — Create a free ticket type for an Eventzilla event with its name, description, quantity, sales window, per-order limits and visibility. Returns the created ticket type with ticket_type_id and the submitted fields. Required: event_id and all ticket type fields except additional_instructions and unlock_code. - **list_all_eventzilla_event_ticket_types** — List the ticket types (and donation options) configured for an Eventzilla event. Returns ticket type records with id, title, description, price, quantity_total, tickets sold, sales start/end dates and times, limits, visibility and box-office flags. Required: event_id. - **update_a_eventzilla_event_ticket_type_by_id** — Update a free ticket type of an Eventzilla event. All ticket type fields must be sent again except additional_instructions and unlock_code. Returns the updated ticket type. Required: event_id, id (the ticket type id). - **eventzilla_event_orders_cancel** — Cancel a pending or completed order for an Eventzilla event, recording the organizer's comments. Returns: ordercancel (status message). Required: event_id, checkout_id, comments. - **eventzilla_event_orders_confirm** — Confirm a pending order for an Eventzilla event (for example an offline or pay-later order), optionally emailing the buyer. Returns: orderconfirm (status message). Required: event_id, checkout_id, comments. - **eventzilla_checkout_orders_confirm** — Confirm an Eventzilla checkout order after it has been filled, setting its payment status and optionally emailing the confirmation. Returns the order with checkout_id, transaction_ref, totals, transaction_status, confirmation_email_sent and currency. Required: event_id, event_date_id, checkout_id, payment_status. - **create_a_eventzilla_checkout_order** — Start an Eventzilla checkout order by reserving ticket types and quantities for an event date, optionally with a discount code. Returns the order with checkout_id, transaction_ref, totals, currency and the reserved tickets (ticket_price_id per ticket). Next call fill, then confirm. Required: event_id, event_date_id, ticket_types. - **eventzilla_checkout_orders_fill** — Fill an Eventzilla checkout order with the buyer details, the attendee details and question answers for each reserved ticket, and the chosen payment option. Returns the order with checkout_id, transaction_ref, totals and tickets. Required: event_id, event_date_id, checkout_id, payment_id, buyerdetails, tickets. - **eventzilla_checkout_orders_prepare** — Prepare a checkout for an Eventzilla event date: returns the ticket types on sale with prices, limits and availability, the registration questions, payment options, and whether discounts and tax apply. Call this first, then create, fill and confirm the order. Required: event_id, date_id. - **eventzilla_attendees_checkin** — Check an attendee in to an Eventzilla event by ticket barcode, or revert a check-in. Returns the attendee's first_name, last_name, eventtitle, orderref, email and the resulting status. Required: barcode, eventcheckin. - **get_single_eventzilla_attendee_by_id** — Get a single Eventzilla attendee by id, including ticket, order and check-in details. Returns: id, first_name, last_name, email, ticket_type, bar_code, is_attended, transaction_ref, transaction_status, event_id, title, buyer names, promo_code, questions. Required: id. - **list_all_eventzilla_attendees** — List attendees of an Eventzilla event with their ticket, order and check-in details. Returns attendee records with id, first_name, last_name, email, ticket_type, bar_code, is_attended, transaction_ref, transaction_status, transaction_date, transaction_amount, buyer names, promo_code and question answers. Required: event_id. - **list_all_eventzilla_event_transactions** — List Eventzilla transactions for a specific event. Returns: transaction_ref, checkout_id, transaction_date, transaction_amount, tickets_in_transaction, event_date, transaction_status, user_id, event_id, title, email, buyer_first_name, buyer_last_name, promo_code, payment_type, comments, transaction_tax, transaction_discount, eventzilla_fee. Required: event_id. Max 100 per page. - **get_single_eventzilla_transaction_by_id** — Get a single Eventzilla transaction by its checkout ID or order reference number. Returns: transaction_ref, refno, checkout_id, transaction_date, transaction_amount, transaction_total, transaction_tax, transaction_discount, eventzilla_fee, currency, transaction_status, tickets_in_transaction, tickets, event_date, event_id, title, user_id, email, buyer_first_name, buyer_last_name, promo_code,… - **get_single_eventzilla_user_by_id** — Get details of a specific Eventzilla user by id. Returns the user object including id, username, first_name, last_name, email, timezone, and user_type. Required: id (user/organizer identifier). - **list_all_eventzilla_users** — List Eventzilla users (organizers and sub-organizers). Returns an array of user records with id, username, first_name, last_name, email, and user_type. ## How it works 1. **Link your customer's Eventzilla account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Eventzilla.** The Proxy API is a 1-to-1 mapping of the Eventzilla API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync event attendees into CRM and marketing automation** — Marketing and CRM platforms can pull Eventzilla attendees (with registration answers and check-in status) to trigger lead scoring, segmentation, and post-event email flows based on whether a registrant actually showed up. - **Automate ticketing revenue reconciliation** — Accounting and finance SaaS tools can ingest granular Eventzilla transactions — gross amount, tax, discount, and platform fees — to automatically map ticketing revenue to the right ledger accounts without manual reconciliation. - **Embed white-labeled event registration** — Association management systems, community platforms, and member portals can offer native ticket purchasing by chaining Eventzilla's prepare → create → fill → confirm checkout flow entirely inside their own UI. - **Power on-site check-in and badge-scanning apps** — Event tech vendors building kiosks, mobile check-in apps, or sponsor lead capture tools can validate barcodes and mark attendees as checked in in real time against the organizer's Eventzilla account. - **Programmatically manage ticket inventory and sales windows** — Event ops platforms can create new ticket types, update capacity and sale windows, and pause or resume sales based on external triggers like waitlist thresholds or sponsorship deadlines. ## What you can build - **Attendee sync with check-in status** — Pull the full attendee list for any event, including custom registration answers and the is_attended flag, and keep it continuously synced with your platform. - **Transaction-level revenue ingestion** — List event transactions and fetch individual transaction details to break out ticket revenue, taxes, discounts, and Eventzilla fees for reporting or accounting workflows. - **Embedded checkout flow** — Build a native ticket purchase experience by orchestrating the prepare, create, fill, and confirm checkout order endpoints without redirecting users off your product. - **Ticket type management console** — Let your users create and update ticket types — including capacity, sale windows, and visibility — directly from your UI using the ticket type endpoints. - **Barcode-based check-in app** — Validate attendee barcodes at the door and toggle check-in status in real time, with the ability to reverse accidental check-ins. - **Sales on/off automation** — Programmatically toggle event sales on or off in response to external signals like inventory levels, approval workflows, or campaign schedules. ## FAQs ### What Eventzilla data objects can I access through Truto? You can access events, event categories, ticket types, attendees, orders, transactions, and users. Each resource supports list and/or get operations, and ticket types, orders, and check-ins additionally support write operations. ### Can I build a fully embedded checkout without redirecting users to Eventzilla? Yes. Eventzilla exposes a four-step checkout flow — prepare, create, fill, and confirm — that lets you reserve inventory, submit buyer and attendee details, and finalize an order entirely from your own UI. ### Does the integration support real-time check-in? Yes. The attendee check-in endpoint lets you mark an attendee as checked in (or revert a check-in) in real time, which is suitable for on-site kiosks and companion mobile apps. ### How are custom registration questions handled? Custom registration answers are returned as part of the attendee object when you list attendees or fetch a single attendee by ID, so you can map them into your own schema downstream. ### Can I get a full financial breakdown for each ticket sale? Yes. The transaction endpoints return granular fields including transaction amount, tax, discount, and Eventzilla fee, which is enough to reconcile gross revenue, net payouts, and fees separately. ### How does Truto handle authentication with Eventzilla? Truto manages the Eventzilla auth handshake and token lifecycle for each of your end users, so your product only needs to call Truto's unified endpoints — you don't handle Eventzilla credentials or refresh logic directly. ### Can I programmatically pause ticket sales for an event? Yes. The toggle sales endpoint lets you publish or unpublish an event's sales status, which is useful for capacity caps, approval gates, or scheduled sales windows driven from your platform.