Eventzilla · Schema

Attendee

An attendee registered for an Eventzilla event.

EventTicketingRegistrationAttendeesEvent Management

Properties

Name Type Description
id numberstring Unique attendee identifier
first_name string Attendee first name
last_name string Attendee last name
email string Attendee email address
ticket_type string Ticket type name
bar_code string Attendee barcode for check-in
is_attended string Check-in status
questions array Registration question answers
transaction_ref string Transaction reference number
refno string Transaction reference number (alternate field)
transaction_date string Date of transaction
transaction_amount numberstring Transaction amount
transaction_status string Transaction status
event_id number Associated event identifier
event_date string Event date
title string Event title
user_id number Organizer user identifier
buyer_first_name string Buyer first name
buyer_last_name string Buyer last name
payment_type string Payment method used
View JSON Schema on GitHub

JSON Schema

attendee.json Raw ↑
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://developer.eventzilla.net/schemas/attendee",
  "title": "Attendee",
  "description": "An attendee registered for an Eventzilla event.",
  "type": "object",
  "properties": {
    "id": { "type": ["number", "string"], "description": "Unique attendee identifier" },
    "first_name": { "type": "string", "description": "Attendee first name" },
    "last_name": { "type": "string", "description": "Attendee last name" },
    "email": { "type": "string", "format": "email", "description": "Attendee email address" },
    "ticket_type": { "type": "string", "description": "Ticket type name" },
    "bar_code": { "type": "string", "description": "Attendee barcode for check-in" },
    "is_attended": { "type": "string", "description": "Check-in status" },
    "questions": {
      "type": "array",
      "description": "Registration question answers",
      "items": {
        "type": "object",
        "properties": {
          "questions": { "type": "string", "description": "Question text" },
          "answer": { "type": "string", "description": "Answer text" }
        }
      }
    },
    "transaction_ref": { "type": "string", "description": "Transaction reference number" },
    "refno": { "type": "string", "description": "Transaction reference number (alternate field)" },
    "transaction_date": { "type": "string", "description": "Date of transaction" },
    "transaction_amount": { "type": ["number", "string"], "description": "Transaction amount" },
    "transaction_status": { "type": "string", "description": "Transaction status" },
    "event_id": { "type": "number", "description": "Associated event identifier" },
    "event_date": { "type": "string", "format": "date-time", "description": "Event date" },
    "title": { "type": "string", "description": "Event title" },
    "user_id": { "type": "number", "description": "Organizer user identifier" },
    "buyer_first_name": { "type": "string", "description": "Buyer first name" },
    "buyer_last_name": { "type": "string", "description": "Buyer last name" },
    "payment_type": { "type": "string", "description": "Payment method used" }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/attendee"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.