# Platypus.Tickets

> Documentation

Reference material for running your venue on Platypus. No pitch, just how it works.

## Table of Contents

### Tenant administration

- [What Platypus does](/guide.md): What Platypus does for a venue — the admin at a glance, and where each feature is documented.
- [Setting up an event](/guide/setting-up-an-event.md): Creating an event — metadata, description, single or multiple dates, and ticket types with pricing and capacity.
- [Tickets, PDFs & the door](/guide/tickets-and-delivery.md): Ticket delivery and the door sheet — the confirmation email and PDF download, issuing tickets yourself from the admin, and when paper beats the scan link.
- [Door check-in](/guide/door-checkin.md): Checking tickets in at the door with a secret scan link — creating and sharing the door link, what staff see, the check-in window, undo, and the printed door sheet fallback.
- [Cancelling, restoring & duplicating events](/guide/event-lifecycle.md): Cancelling events — what ticket buyers see, why refunds and buyer contact are your job, hiding a cancelled listing, and recovering with restore or duplicate.
- [Ticket Office](/guide/ticket-office.md): The Ticket Office — closing online sales now or at a set time, the public message, reopening, the automatic close after the event day, and what the audit log records.
- [Mailing list & campaigns](/guide/mailing-list.md): Building and using your subscriber list — how people join and leave, adding and importing subscribers, tags, sending email campaigns, and phone capture.
- [Contact form](/guide/contact-form.md): The public contact form — what visitors see, where messages are delivered, the Contact Form Inbox setting, and what to check when messages stop arriving.
- [Customer segments](/guide/customer-segments.md): Customer segments, discounts, and voucher codes — every mailing-list tag is a segment, discounts live on each event's Discounts tab, and every discount is a code the buyer enters at checkout.
- [Reports](/guide/reports.md): The Reports section — sales and revenue, page views, mailout delivery, checkout issues and broken links, the admin-only audit log, and CSV exports.
- [Mail settings](/guide/mail-settings.md): Choosing the provider that sends your email — Platypus hosted mail vs your own Mailgun, Resend, SendGrid, or SMTP account, the From address, what every email says about you, the test send, and troubleshooting.
- [Subscription & billing](/guide/subscription-and-billing.md): Your Platypus subscription — plans, the per-ticket fee and its price bands, managing payment and invoices, and what the subscription does (and doesn't) control.
- [Stripe payments setup](/guide/stripe-payments.md): Connecting your Stripe account so the Ticket Office can take payments on your behalf — keys, webhook, test mode, go-live checklist, and troubleshooting.
- [Payment exceptions](/guide/payment-exceptions.md): Payment exceptions — what each flag on the Payments page means, how to refund the buyer in Stripe, and when to mark the record resolved.
- [Business identity](/guide/business-identity.md): Your ABN and ticket terms & refund policy — where to set them and where buyers see them.
- [Timezone](/guide/timezone.md): The venue timezone — where to set it, the day-boundary decisions it drives, reminder due days, and touring stops that carry their own zone.
- [Account security](/guide/account-security.md): Protecting your admin account — changing your password from inside the admin, setting up multi-factor authentication with an authenticator app, recovery codes, and what to do if you're locked out.
- [Team users](/guide/team-users.md): Sharing the admin with your team — the five roles and what each can do, inviting users by email, deactivating vs deleting, setting or resetting a teammate's password or MFA, and why the admin account can never be locked out.
- [Appearance & custom CSS](/guide/appearance.md): The Settings > Appearance tab — writing custom CSS for your public pages, the stable selector contract (page IDs, layout hooks, repeating classes), and the disableCustomCss debugging switch.

### Developer reference

- [Introduction](/api.md): The Platypus.Tickets public event API — base URL, response format, what is and isn't supported, and CORS rules.
- [Event endpoints](/api/events.md): The two public event endpoints — list events and fetch one event — with real request and response examples.
- [Embedding on your site](/api/embeds.md): Embedding Platypus event details, the Ticket Office, and your events listing on your own website with iframes.
- [Appearance & custom CSS](/api/appearance-css.md): The stable CSS selector contract for styling embedded Platypus pages — page IDs, layout hooks, repeating classes, and the disableCustomCss debugging switch.

### FAQ

- [About Platypus](/faq.md): What Platypus.Tickets is — who it's for, how it's priced, and who runs it.
- [Stripe and payments](/faq/stripe.md): How Platypus uses Stripe — venue-owned payments, what buyers see, and what venues need.
- [Features](/faq/features.md): What Platypus does — the audience-facing pages and checkout, and the venue-side admin tools.
- [Feature suggestions](/faq/suggestions.md): Feature suggestions — the public ideas board, voting on other venues' ideas, and what belongs there.
- [Sign-ups](/faq/sign-ups.md): How venues join Platypus — request an account, we review it personally, and your admin arrives by email invitation.
- [Contact & support](/faq/support.md): How to reach Platypus support — the support inbox, what to include, and what we can and can't do.
- [About these docs](/faq/about-these-docs.md): How this documentation stays true to the running system — build stamps, test-backed examples, and coverage gates.