Skip to main content
This walkthrough creates a ticketed event, adds ticket types to it, publishes it, and registers attendees. The chain covers the Event, ProductPrice and EventAttend resources. Buyers pay through the public checkout described in Build a public event landing page. Who is this for: integrations that need to provision events programmatically (recurring training, partner-organized meetups, automated festival setup) or surface Orgo’s ticketing in a custom site.

Prerequisites

  • Stripe connected for the organization or the event’s local center, see Stripe integration. Without it, free tickets still work.
  • An Api-Token from a user who may create events and enable ticketing (an administrator, or someone with organization-wide event rights) and create prices (organization-wide or chapter finance rights). Without those rights, hasEventTicketing is quietly turned off on creation, or the price call answers 403.

Step 1: Create the event as a draft

New events are always created as drafts, invisible to members and the public. You can edit freely until you publish. You do not send a status; the server sets it.
The response carries an integer id and a uuid. Events are addressed by uuid in their paths (/api/v1/events/{uuid}), so keep it. Setting hasEventTicketing: true creates the event’s ticketing product for you; the response shows it in product.
Event statuses are lowercase (draft, published). If the dates are already in the past the event is created as published. A public event inside a group that is not joinable is forced to private.

Step 2: Add ticket types

A ticket type in Orgo is a price on the event’s product, not a product of its own. One event, one product, one ProductPrice per ticket type (general admission, member, early bird).
price is in currency units (25.00 is twenty-five dollars), not cents. A price of 0 makes a free ticket. maxSeats caps how many of this ticket can be sold; leave it out for no cap beyond the event’s maxCapacity. The optional sales window (validFrom, validTo) cannot start before the event was created or end after the event ends, otherwise the call answers 400. When a Stripe account is connected, the price is synced to Stripe. Other useful fields: groupName (to group tickets on the page), isRestricted and allowedFeeProductPrices (members-only tickets), ageUnder and ageOver, isHidden. Repeat the call for each ticket type; the response returns the price id that buyers reference in checkout.
To retire a ticket type, set isArchived: true with PATCH /api/v1/product_prices/{id}. Archived tickets are no longer offered at checkout.

Step 3: Publish the event

Publishing flips the event from draft to published, creates a notification and, for future events, tells the unit’s members. It fails if the event is already published.
After publishing, anyone can read the event with GET /api/v1/get_public_event_anonymous/{uuid} and the public registration page lives at https://acme.orgo.space/public/event/{uuid}. Before you publish, organizers can preview the page with a draft preview link (PATCH /api/v1/events/{uuid}/preview-token) and see ticket availability with GET /api/v1/events/{uuid}/draft-availability.
/api/v1/event-go-publish/{uuid} is the publish call used by the “Go” landing-page editor. Use events_publish from server-to-server integrations.

Step 4: Register attendees

Buyers register and pay through the public checkout. For people you register yourself, there are two paths.

Path A: an existing member

When the target user is not the caller, the registration is an invitation: the member gets an email, and for events with a registration form their answer is awaited. The response carries the attendance id, statusRsvp, statusRegistration (invited or success) and a hash that doubles as the QR check-in code. Duplicates are refused, and non-ticketed events respect maxCapacity.

Path B: a person with no account

Invite them by email. Orgo matches the address against members first, then contacts, and creates a contact if neither exists:
Note that event here is the event’s uuid, not an IRI, and the fields sit inside entity. The recipient receives a link they can open without an account. With skipEmail: true no email is sent and you register them on their behalf, then confirm them (below).

Confirming an invited attendee

For VIP, speaker or complimentary access, confirm the invitation yourself. This upgrades the attendee to success and emails them a ticket with a QR code:

Step 5: Payments

For paid tickets the buyer pays on the public checkout, where Stripe collects the card and Orgo records a ProductPayment. You never create the charge yourself. When the payment clears, the attendance becomes success and a ticket is emailed. React to it with the product_payment.updated and event_attend.created webhooks, see Handle webhooks. Refunding a payment cancels the linked registration and returns the seat to the pool, see Process payments.

Check-in on the day

At the venue, scan the attendee’s QR code in the Orgo event app, or mark them attended through the API:
RSVP states are attending, maybe, not_attending and attended. Setting statusRegistration to success by hand checks that payment is complete and the required form fields are filled, unless the caller manages the event.

Common gotchas

The public page only exists for events that are published and isPublic: true. Members-only events have no public page at all.
hasEventTicketing is only honored for callers with organization-wide event or finance rights. For anyone else the event is created without ticketing, with no error. Check the flag in the response.
Paid tickets need a connected Stripe account for the organization or the event’s local center, see Stripe integration.
Set hasEventTicketing: true and requiresRegistrationForm: true, and create a ticket price with price: 0. Payment is skipped for a zero total, and the buyer completes with complete-free on the public checkout.
Yes. After the main attendee is confirmed (statusRegistration: success), call POST /api/v1/event_attends/{id}/guest-tickets with {"quantity": 3}. A request takes 1 to 20 guests, and each guest ticket is generated as a PDF and emailed.

What to do next