Pp Eventbrite

<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/media-and-entertainment/eventbrite/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Eventbrite — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the eventbrite-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install eventbrite --cli-only

2. Verify: eventbrite-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

go install github.com/mvanhorn/printing-press-library/library/media-and-entertainment/eventbrite/cmd/eventbrite-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

When to Use This CLI

Use this CLI when an agent manages an organizer's Eventbrite presence: creating and publishing events, pulling order and attendee history, and answering cross-event questions (which events sell slowest, which fans return, who the top buyers are, how a discount code performed) that the per-event dashboard and existing single-org MCP servers cannot answer. It is the right tool whenever the task needs the whole order/attendee history in one place rather than a single live API lookup. When the same promoter also sells on DICE, both CLIs emit JSON and a local SQLite store, so an agent can join the two datasets by event (name and date) and by buyer email for a cross-platform performance and loyalty picture.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Cross-event sales analytics

• `sales-velocity` — Ranks all your live events by tickets sold per day since on-sale and projects a sell-out date.

_Reach for this when an agent needs to know which of an organizer's events are underperforming right now, not just current totals._

  eventbrite-pp-cli sales-velocity --json

• `discount-performance` — Per discount code: redemptions, type, and the redemption rate (share of the code's allotment used).

_Pick this to measure whether a promo code actually drove sales before renewing or killing it._

  eventbrite-pp-cli discount-performance --json

• `capacity` — Sold vs total capacity and percent remaining across all your live events at once.

_Use this to spot which events are near sell-out or badly under-sold in a single call._

  eventbrite-pp-cli capacity --json

• `refund-rate` — Refunded and cancelled order counts, refunded revenue, and the rate per event or across the org.

_Pick this to flag events with abnormal refund rates that signal a pricing, date, or fulfillment problem._

  eventbrite-pp-cli refund-rate --json

• `top-buyers` — Ranks ticket buyers by total spend across all your events, not just by how many events they attended.

_Reach for this to find an organizer's highest-value customers for VIP or pre-sale outreach._

  eventbrite-pp-cli top-buyers --limit 25 --json

Search your own data offline

• `repeat-attendees` — Finds fans who bought into two or more of your events, across your whole synced history.

_Use this for loyalty and re-marketing questions an agent cannot answer from any one event's attendee list._

  eventbrite-pp-cli repeat-attendees --min 2 --json

• `roster` — Offline attendee roster for one event with checked-in vs not-yet, VIP and comp flags, door-sorted.

_Reach for this at the door when an agent needs a fast who-has-not-checked-in list without a live API round-trip._

  eventbrite-pp-cli roster 1234567890 --csv

• `fan-export` — Exports unique attendee contacts (email, name, events attended, check-in status), deduped across all your events and filterable by event.

_Use this to build a clean, deduped contact list for an email campaign across an organizer's whole audience._

  eventbrite-pp-cli fan-export --csv

Agency multi-org view

• `org-rollup` — Single pane across every organization your token can see: events count, tickets sold, gross, and top event per org.

_Use this for an agency or multi-brand operator who needs one client roll-up instead of logging into each org._

  eventbrite-pp-cli org-rollup --json

Command Reference

balance — Manage balance

categories — <a name="categories_object"></a>

Category Object

An overarching category that an event falls into (vertical). Examples are “Music”, and “Endurance”.

• eventbrite-pp-cli categories category-by-id — Gets a category by ID as `category`.
• eventbrite-pp-cli categories list-of — Returns a list of Category as categories, including subcategories nested. Returns a paginated response.

discounts — <a name="discount_object"></a>

Discount Object

The Discount object represents a discount that an Order owner can use when purchasing tickets to an Event.

A Discount can be used to a single Ticket Class or across multiple Ticket Classes for multiple Events simultaneously (known as a cross event Discount).

There are four types of Discounts:

+ Public Discount. Publically displays Discount to Order owner on the Event Listing and Checkout pages. Only used with a single Event.

+ Coded Discount. Requires Order owner to use a secret code to access the Discount.

+ Access Code. Requires Order owner to use a secret code to access hidden tickets. Access codes can also optionally contain a discount amount.

+ Hold Discount. Allows Order owner to apply or unlock Discount for seats on hold.

The display price of a ticket is calculated as: \ price_before_discount - discount_amount = display_price

Notes:

• Public and Coded Discounts can specify either an amount off or a percentage off, but not both types discounts.

• Public Discounts should not contain apostrophes or non-alphanumeric characters (except “-���, “_”, ” ”, “(”, ”)”, “/”, and “”).

• Coded Discounts and Access Codes should not contain spaces, apostrophes or non-alphanumeric characters (except “-”, “_”, “(”, ”)”, “/”, and “”).

Fields

Use these fields to specify information about a Discount.

The following conditions define the extend of the Discount:

• If event_id is provided and ticket_class_ids are not provided, a single Event Discount is created for all Event tickets.

• If both event_id and ticket_class_ids are provided, a single Event Discount is created for the specific Event tickets.

• If ticket_group_id is provided, a Discount is created for the Ticket Group.

• If neither event_id nor ticket_group_id are provided, a Discount is created that applies to all tickets for an Organization's Events, including future Events.

Expansions

Information from expansions fields are not normally returned when requesting information. To receive this information in a request, expand the request.

• eventbrite-pp-cli discounts delete-a — Delete a Discount. Only unused Discounts can be deleted.
• eventbrite-pp-cli discounts retrieve-a — Retrieve a Discount by Discount ID.
• eventbrite-pp-cli discounts update-a — Update a Discount by Discount ID.

event — <a name="event_object"></a>

Event Object

The Event object represents an Eventbrite Event. An Event is owned by one Organization.

Public Fields

Use these fields to specify information about an Event. For publicly listed Events, this information can be retrieved by all Eventbrite Users and Eventbrite applications.

Private Fields

Use these fields to specify properties of an Event that are only available to the User.

<a name="music_properties_object"></a>

Music Properties

The Music Properties object includes a few attributes of an event for Music clients. To retrieve Music Properties by Event ID, use the music_properties expansion.

<a name="event_expansions" />

Expansions

Information from expansions fields are not normally returned when requesting information. To receive this information in a request, expand the request.

events — <a name="event_object"></a>

Event Object

The Event object represents an Eventbrite Event. An Event is owned by one Organization.

Public Fields

Use these fields to specify information about an Event. For publicly listed Events, this information can be retrieved by all Eventbrite Users and Eventbrite applications.

Private Fields

Use these fields to specify properties of an Event that are only available to the User.

<a name="music_properties_object"></a>

Music Properties

The Music Properties object includes a few attributes of an event for Music clients. To retrieve Music Properties by Event ID, use the music_properties expansion.

<a name="event_expansions" />

Expansions

Information from expansions fields are not normally returned when requesting information. To receive this information in a request, expand the request.

• eventbrite-pp-cli events delete-an — Delete an Event if the delete is permitted. Returns a boolean indicating the success or failure of the delete action.
• eventbrite-pp-cli events retrieve-an — Retrieve an Event by Event ID.
• eventbrite-pp-cli events update-an — Update Event by Event ID.

formats — <a name="formats_object"></a>

Format Object

The Format object represents an Event type, for example seminar, workshop or concert. Specifying a Format helps website visitors discover a certain type of Event.

• eventbrite-pp-cli formats list — List all available Formats. Returns a paginated response.
• eventbrite-pp-cli formats retrieve-a — Retrieve a Format by Format ID.

media — <!-- Here is a tutorial on Media Upload in EventBrite. -->

<a name="media_object"></a>

Media Object

The Media object represents an image that can be included with an Event listing, for example to provide branding or further information on the Event.

• eventbrite-pp-cli media retrieve — Retrieve Media by Media ID.
• eventbrite-pp-cli media retrieve-a-upload — Retrieve information on a Media image upload.
• eventbrite-pp-cli media upload-a-file — Upload a Media image file.

orders — <a name="order_object"></a>

Order object

The Order object represents an order made against Eventbrite for one or more Ticket Classes. In other words, a single Order can be made up of multiple tickets. The object contains an Order's financial and transactional information; use the Attendee object to return information on Attendees.

Order objects are considered private; meaning that all Order information is only available to the Eventbrite User and Order owner.

Order Fields

<a name="order_cost"></a>

Order Costs Fields

Contains a breakdown of Order costs.

<a name="order_display_tax"></a>

Display Tax Fields

Refund Request Fields

The Order includes a refund request.

<a name="refund_item"></a>

Refund Item Fields

A Refund Request contains a refund item.

<a name="order_questions"></a>

Order Questions Fields

Use to present Custom Questions to an Attendee.

<a name="order_answers"></a>

Order Answers Fields

Contains information on an Attendee's answers to custom questions.

Order Notes Fields

Order Notes is free-form text related to an Order.

Expansions

Information from expansions fields are not normally returned when requesting information. To receive this information in a request, expand the request.

• eventbrite-pp-cli orders <order_id> — Retrieve an Order by Order ID.

organizations — <a name="organization_object"></a>

Organization Object

An object representing a business structure (like a Marketing department) in which Events are created and managed. Organizations are owned by one User and can have multiple Members.

The Organization object is used to group Members, Roles, Venues and Assortments.

Public Fields

Use these fields to specify information about an Organization.

pricing — <a name="Pricing_object"></a>

Pricing Object

The Pricing object represents all the available fee rates for different currencies, countries, Assortments and sales channels.

• eventbrite-pp-cli pricing calculate-items — Calculates the Fees that Eventbrite would charge for a given price as it’s shown on the ticket authoring flow.
• eventbrite-pp-cli pricing list — List all available Pricing rates. Returns a paginated response.

reports — <a name="reports_object"></a>

Report Object

The Report object represents the Reports that you can retrieve using the API. This includes Reports on:

+ Sales activity

+ Attendees for an Event.

• eventbrite-pp-cli reports retrieve-a-attendee — Retrieve an Attendee Report by Event ID or Event status.
• eventbrite-pp-cli reports retrieve-a-sales — Retrieve a sales Report by Event ID or Event status.

series — Manage series

• eventbrite-pp-cli series <event_series_id> — Retrieve the parent Event Series by Event Series ID.

subcategories — Manage subcategories

• eventbrite-pp-cli subcategories list-of — List all available Subcategories. Returns a paginated response.
• eventbrite-pp-cli subcategories subcategory-by-id — Retrieve a Subcategory by Subcategory ID.

ticket-groups — <a name="ticket_group_object"></a>

Ticket Group Object

The Ticket Group object is used to group Ticket Classes.

Most commonly used to apply a Cross-Event Discount to multiple Ticket Classes.

Fields

• eventbrite-pp-cli ticket-groups delete-a — Delete a Ticket Group. The status of the Ticket Group is changed to deleted.
• eventbrite-pp-cli ticket-groups retrieve-a — Retrieve a Ticket Group by Ticket Group ID.
• eventbrite-pp-cli ticket-groups update-a — Update Ticket Group by Ticket Group ID.

users — >Note: Note These URLs will accept “me” in place of a user ID in URLs - for example, /users/me/orders/ will return orders placed by the current user.

<a name="user_object"></a>

User Object

User is an object representing an Eventbrite account. Users are Members of an Organization.

• eventbrite-pp-cli users list-your-organizations — List the Organizations to which you are a Member. Returns a paginated response.
• eventbrite-pp-cli users retrieve-information-about-a-account — Returns a user for the specified user as user.
• eventbrite-pp-cli users retrieve-information-about-your-account — Retrieve Information About Your User Account

venues — <a name="venue_object"></a>

Venue Object

The Venue object represents the location of an Event (i.e. where an Event takes place).

Venues are grouped together by the Organization object.

Venue Fields

• eventbrite-pp-cli venues retrieve-a — Retrieve a Venue by Venue ID.
• eventbrite-pp-cli venues update-a — Update a Venue by Venue ID.

webhooks — <a name="webhooks_object"></a>

Webhook Object

An object representing a webhook associated with the Organization.

• eventbrite-pp-cli webhooks create-deprecated — Create a Webhook. > Warning: Access to this API will be no longer usable on June 1st, 2020.
• eventbrite-pp-cli webhooks delete-by-id — Delete a Webhook by ID.
• eventbrite-pp-cli webhooks list-of-deprecation — List Webhooks. > Warning: Access to this API will be no longer usable on June 1st, 2020.

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

eventbrite-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Find your slowest-selling live events

eventbrite-pp-cli sales-velocity --json

Ranks every live event by tickets sold per day since on-sale with a projected sell-out date, computed from the local order store.

Surface returning fans for re-marketing

eventbrite-pp-cli repeat-attendees --min 3 --agent --select email,name,events_count

Cross-event attendee join; --agent emits structured rows and --select narrows to just the contact fields an email tool needs.

Door check-in roster, offline

eventbrite-pp-cli roster 1234567890 --csv

Prints the synced attendee roster for one event with checked-in status as CSV for a will-call sheet — no live API call required.

Agency Friday client roll-up

eventbrite-pp-cli org-rollup --json

One pane across every organization the token can see: events, tickets sold, gross, and top event per client org.

Measure a promo code's ROI

eventbrite-pp-cli discount-performance --json

Ranks discount codes by redemptions and redemption rate (share of each code's allotment used) from the synced discount objects.

Combine Eventbrite + DICE for full event performance

eventbrite-pp-cli fan-export --json

Export your Eventbrite buyer/attendee list as JSON; a promoter selling the same show on DICE exports the DICE side too, then an agent joins events by name and date and buyers by normalized email for a cross-platform performance and loyalty view no single platform shows.

Auth Setup

Eventbrite uses an OAuth2 private token sent as a Bearer header. For your own account you do not need the full OAuth dance — copy a private token from eventbrite.com/platform/api-keys and set EVENTBRITE_API_KEY. Run eventbrite-pp-cli doctor to confirm it is picked up.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr
• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  eventbrite-pp-cli formats list --agent --select id,name,status

• Previewable — --dry-run shows the request without sending
• Offline-friendly — sync/search commands can use the local SQLite store when available
• Non-interactive — never prompts, every input is a flag
• Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

eventbrite-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
eventbrite-pp-cli feedback --stdin < notes.txt
eventbrite-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.eventbrite-pp-cli/feedback.jsonl. They are never POSTed unless EVENTBRITE_FEEDBACK_ENDPOINT is set AND either --send is passed or EVENTBRITE_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

eventbrite-pp-cli profile save briefing --json
eventbrite-pp-cli --profile briefing formats list
eventbrite-pp-cli profile list --json
eventbrite-pp-cli profile show briefing
eventbrite-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Argument Parsing

Parse $ARGUMENTS:

1. Empty, `help`, or `--help` → show eventbrite-pp-cli --help output 2. Starts with `install` → ends with mcp → MCP installation; otherwise → see Prerequisites above 3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

1. Install the MCP server:

   go install github.com/mvanhorn/printing-press-library/library/media-and-entertainment/eventbrite/cmd/eventbrite-pp-mcp@latest

2. Register with Claude Code:

   claude mcp add eventbrite-pp-mcp -- eventbrite-pp-mcp

3. Verify: claude mcp list

Direct Use

1. Check if installed: which eventbrite-pp-cli If not found, offer to install (see Prerequisites at the top of this skill). 2. Match the user query to the best command from the Unique Capabilities and Command Reference above. 3. Execute with the --agent flag:

   eventbrite-pp-cli <command> [subcommand] [args] --agent

4. If ambiguous, drill into subcommand help: eventbrite-pp-cli <command> --help.