pp-eventbrite

What this skill does

<!-- 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:
   ```bash
   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):

```bash
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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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._

  ```bash
  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](#event_object).

A Discount can be used to a single [Ticket Class](#ticket_class_object) 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.

|         Field         |       Type       |                                                                                              Description                                                                                              |
| :-------------------- | :--------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `code`                | `string`         | Discount name for a Public Discount, or the code for a Coded Discount and Access Code.                                                                                                                |
| `type`                | `string`         | Discount type. Can be `access`, `coded`, `public` or `hold`.                                                                                                                                          |
| `end_date`            | `datetime`       | Date until which