# Orriven Help Center

## Docs

- [Welcome to Orriven](https://docs.orriven.com/en/index.md): An event operations platform for organizers — registration, ticketing, agenda, exhibition, housing and email in one console.
- [Quickstart](https://docs.orriven.com/en/quickstart.md): From a new account to a published event taking registrations, in seven steps.
- [Core concepts](https://docs.orriven.com/en/concepts.md): The vocabulary Orriven is built on — organizations, business units, events, portals, registrations, attendees, contacts, orders and perks.
- [Business Units](https://docs.orriven.com/en/organization/business-units.md): The team that runs events — its own members, roles, settings, content and public portal, inside your organization.
- [Members & roles](https://docs.orriven.com/en/organization/members-roles.md): Invite people at the organization level, give them a default role, and override it per business unit where needed.
- [Audit log](https://docs.orriven.com/en/organization/audit-logs.md): Every change made in the console, recorded automatically — who did what, to which object, and when.
- [Create an event](https://docs.orriven.com/en/events/create-event.md): Create an event inside a Business Unit, choose where it publishes, and understand what the start date controls.
- [The event page](https://docs.orriven.com/en/events/event-page.md): How the public side of an event works: portals, themes, draft versus published, the event URL and attendee accounts.
- [Attendees](https://docs.orriven.com/en/events/attendees.md): The registrations list, adding attendees from the console, approval and waitlist statuses, and the attendee detail page.
- [Event settings](https://docs.orriven.com/en/events/settings.md): Basic details and schedule, event status, optional feature modules like Exhibition and Housing, and the event-level audit log.
- [Ticket types](https://docs.orriven.com/en/ticketing/ticket-types.md): Define how people register: capacity, sale windows, visibility, waitlists and approval — each as its own ticket type.
- [Registration forms](https://docs.orriven.com/en/ticketing/registration-form.md): Build the questions attendees answer at checkout, attach a form to each ticket type, and read the answers on the attendee's page.
- [Offers & redemptions](https://docs.orriven.com/en/ticketing/offers.md): Redemption codes that unlock a ticket type: invite guests to hidden tickets, reopen closed registration for the right people, and track every use.
- [Add-ons](https://docs.orriven.com/en/ticketing/addons.md): Extras attendees pick up alongside a ticket — a breakfast voucher, a workshop seat — delivered as the perks the add-on grants.
- [Bundles](https://docs.orriven.com/en/ticketing/bundles.md): Package ticket types and add-ons into one purchase — the buyer receives each item's own registrations and perks.
- [Orders](https://docs.orriven.com/en/ticketing/orders.md): Every purchase from the event page — tickets, add-ons, bundles, even free ones — arrives as an order you can track from the console.
- [Refund policies](https://docs.orriven.com/en/ticketing/refund-policies.md): Named refund ladders you define once and apply to ticket types, add-ons and bundles — today the published promise, money enforcement later.
- [Perks](https://docs.orriven.com/en/ticketing/perks.md): Define a benefit once — a breakfast voucher, lounge access — then grant it from tickets, codes and add-ons, and require it at sessions and venues.
- [Agenda](https://docs.orriven.com/en/program/agenda.md): Build your event's schedule from sessions — titled slots on the calendar, ordered purely by time, with entry controlled through perks.
- [Speakers](https://docs.orriven.com/en/program/speakers.md): A speaker is an attendee with a profile — invite them like any guest, mark them as a speaker, then assign their sessions from one place.
- [Venues](https://docs.orriven.com/en/program/venues.md): The rooms and stages of your event. A venue's perks are its entry gate, and its admit list follows the agenda automatically.
- [Exhibition overview](https://docs.orriven.com/en/exhibition/overview.md): Run the trade-show side of an event: exhibitors, booths, booth types and orderable services. An optional module, off by default.
- [Exhibitors](https://docs.orriven.com/en/exhibition/exhibitors.md): Manage the companies exhibiting at your event: profile, contacts, staff roster, badge codes, booths, service orders and the confirmation lifecycle.
- [Booths](https://docs.orriven.com/en/exhibition/booths.md): The physical booth inventory: every unit has a hall, a number and a type — and allocating one to an exhibitor happens on its page.
- [Booth types](https://docs.orriven.com/en/exhibition/booth-types.md): The booth catalog, defined once: a type describes what a booth is — the booths under it are the actual inventory.
- [Services & materials](https://docs.orriven.com/en/exhibition/services.md): The catalog of things exhibitors order for their booths — power, furniture, lead scanners — and the orders recorded against each item.
- [Housing overview](https://docs.orriven.com/en/housing/overview.md): How the Housing module models hotel accommodation: hotels, room types, room blocks and stays — and the order to set them up in.
- [Hotels and room types](https://docs.orriven.com/en/housing/hotels.md): Add the properties you contract rooms with, manage each hotel's room types, and archive what is no longer taking bookings.
- [Room blocks](https://docs.orriven.com/en/housing/room-blocks.md): Record what you contracted with each hotel — n rooms of one room type per night — and watch pickup against it.
- [Stays](https://docs.orriven.com/en/housing/stays.md): One attendee's hotel reservation: nights, room block attribution, the hotel's answer, check-in — and the CSV export that is your rooming list.
- [Email templates](https://docs.orriven.com/en/marketing/email-templates.md): Design an email once — content, subject and variables — then send it from the Emails page or from an automation.
- [Sending email](https://docs.orriven.com/en/marketing/emails.md): A send is a template resolved against an audience: pick recipients, set variable values, preview per person, confirm, and keep the delivery record.
- [Cohorts](https://docs.orriven.com/en/marketing/cohorts.md): Named attendee groups — hand-picked or rule-driven — built once and applied from any email send draft.
- [Automations](https://docs.orriven.com/en/marketing/automations.md): When something happens in your event, run a flow on its own: a trigger, a canvas of steps, and real email going out without you.
- [Developer API overview](https://docs.orriven.com/en/developers/overview.md): Integrate Orriven with your own systems: manage events, ticket types, registrations, codes and check-ins over a REST API scoped to one Business Unit.
- [API keys](https://docs.orriven.com/en/developers/api-keys.md): Generate, use and revoke developer keys — a key is full API access to one Business Unit, and its secret is shown exactly once.
- [API quickstart](https://docs.orriven.com/en/developers/quickstart.md): From a fresh key to a checked-in attendee: create an event, price a ticket, watch remaining seats, register someone and scan them in.
- [Headless checkout](https://docs.orriven.com/en/developers/checkout.md): Sell tickets on your own website: place an order from your backend, hand the buyer a Stripe payment page, and build their account area from the API.
- [Versioning](https://docs.orriven.com/en/developers/versioning.md): Date-based API versions: your key is pinned to a version at creation, breaking changes ship as new dates, and old integrations keep working unchanged.
- [Endpoint reference](https://docs.orriven.com/en/developers/api-reference.md): Every resource of the Developer API — methods, paths, status codes, the error envelope, and rate limits.
- [List events](https://docs.orriven.com/en/api/events/list-events.md): Every event in the key's business unit, all statuses included.
- [Create an event](https://docs.orriven.com/en/api/events/create-an-event.md): Born `draft` on the business unit's own portal. Publish via PATCH once it has a start time.
- [Get one event](https://docs.orriven.com/en/api/events/get-one-event.md)
- [Update an event](https://docs.orriven.com/en/api/events/update-an-event.md): The console's rules apply: currency locks once ordered; publishing needs a start time; moving the start date clears the agenda and must be confirmed with `confirmAgendaReset`.
- [Archive an event](https://docs.orriven.com/en/api/events/archive-an-event.md): Events are archived, never deleted. Idempotent.
- [List ticket types](https://docs.orriven.com/en/api/ticket-types/list-ticket-types.md)
- [Create a ticket type](https://docs.orriven.com/en/api/ticket-types/create-a-ticket-type.md): Born `draft` — invisible and without effect until opened via PATCH.
- [Get one ticket type](https://docs.orriven.com/en/api/ticket-types/get-one-ticket-type.md)
- [Update a ticket type](https://docs.orriven.com/en/api/ticket-types/update-a-ticket-type.md): Statuses move `draft → open ⇄ closed → archived`; repricing never rewrites sold orders. There is no DELETE — a ticket type's life ends at `archived`.
- [Remaining seats](https://docs.orriven.com/en/api/ticket-types/remaining-seats.md): Organizer-side numbers (the public page only ever learns a boolean). Advisory: no lock is held across this response — the binding capacity check runs inside the purchase and registration transactions.
- [List registrations](https://docs.orriven.com/en/api/registrations/list-registrations.md)
- [Create a registration](https://docs.orriven.com/en/api/registrations/create-a-registration.md): The API keying someone in. An approval-mode ticket type lands the registration `pending` — unlike the console, the API is not an admission decision. A full type answers 412 (or lands `waitlisted` when the type allows it). Registering an email already in the event acknowledges with `created: false`,…
- [Get one registration](https://docs.orriven.com/en/api/registrations/get-one-registration.md)
- [Approve a pending registration](https://docs.orriven.com/en/api/registrations/approve-a-pending-registration.md): Only `pending` moves — anything else answers 412.
- [Reject a pending registration](https://docs.orriven.com/en/api/registrations/reject-a-pending-registration.md)
- [Cancel a registration](https://docs.orriven.com/en/api/registrations/cancel-a-registration.md): Releases the seat (and the redemption-code use, if one admitted them). Already cancelled or rejected answers 412.
- [A registration's effective perks](https://docs.orriven.com/en/api/registrations/a-registrations-effective-perks.md): The union that actually applies to this person: the ticket type's perks ∪ the redemption code's ∪ their own individual grants. Read-only — bindings are edited in the console, from the granting side.
- [List redemption codes](https://docs.orriven.com/en/api/redemption-codes/list-redemption-codes.md)
- [Mint redemption codes](https://docs.orriven.com/en/api/redemption-codes/mint-redemption-codes.md): A code grants *access* to its ticket type, never a place — capacity and sale windows still apply. A custom `code` colliding with an existing one answers 409.
- [Validate a code](https://docs.orriven.com/en/api/redemption-codes/validate-a-code.md): The pre-checkout preview: what a buyer's code unlocks — the ticket (hidden ones included), the perks the admission carries, and the discounted price. Misspelt, disabled, expired, spent and pointing-at-a-closed-type are all the **same** 404 — the caller can never learn which. A valid code still grant…
- [Disable a code](https://docs.orriven.com/en/api/redemption-codes/disable-a-code.md): Codes are disabled, never deleted. Idempotent.
- [List add-ons](https://docs.orriven.com/en/api/add-ons/list-add-ons.md)
- [Create an add-on](https://docs.orriven.com/en/api/add-ons/create-an-add-on.md): Born `draft`. What an add-on delivers is its perk bindings (console-managed).
- [Get one add-on](https://docs.orriven.com/en/api/add-ons/get-one-add-on.md)
- [Update an add-on](https://docs.orriven.com/en/api/add-ons/update-an-add-on.md)
- [List bundles](https://docs.orriven.com/en/api/bundles/list-bundles.md)
- [Create a bundle](https://docs.orriven.com/en/api/bundles/create-a-bundle.md): Only the name on the box — set the contents with PUT …/items. The bundle grants nothing itself; the buyer receives each item's own registrations and perks.
- [Get one bundle](https://docs.orriven.com/en/api/bundles/get-one-bundle.md)
- [Update a bundle](https://docs.orriven.com/en/api/bundles/update-a-bundle.md)
- [Replace the bundle's contents](https://docs.orriven.com/en/api/bundles/replace-the-bundles-contents.md): Every item must be a real ticket type or add-on of this event.
- [List orders](https://docs.orriven.com/en/api/orders/list-orders.md)
- [Place an order](https://docs.orriven.com/en/api/orders/place-an-order.md): The headless cart's settlement: tickets, add-ons and bundles in one order, with an optional redemption code. The order holds its places for 15 minutes until confirmed. A buyer already registered in the event is acknowledged (`alreadyRegistered: true`) — never sold a second seat, never shown an error…
- [Get one order](https://docs.orriven.com/en/api/orders/get-one-order.md)
- [Confirm an order](https://docs.orriven.com/en/api/orders/confirm-an-order.md): A free order settles right here and fulfils into its registration(s). A paid order is claimed instead (`status: "awaiting_payment"`, hold stretched to 35 minutes) and the answer carries the hosted Stripe page to pay on — `successUrl`/`cancelUrl` say where Stripe sends the buyer back on your site. Se…
- [Cancel an order](https://docs.orriven.com/en/api/orders/cancel-an-order.md): Releases the hold now rather than in 15 minutes. Only an unsettled order (pending / awaiting payment) can be cancelled; cancelling twice acknowledges.
- [List check-ins](https://docs.orriven.com/en/api/check-ins/list-check-ins.md)
- [Record a check-in](https://docs.orriven.com/en/api/check-ins/record-a-check-in.md): Idempotent per (registration, door): a second scan acknowledges with `alreadyCheckedIn: true`, never duplicates, never errors. The one hard stop is a registration that is not `confirmed` (412) — the perk verdict stays advisory, exactly as at the console desk.
- [List the event's people](https://docs.orriven.com/en/api/attendees/list-the-events-people.md)
- [List venues](https://docs.orriven.com/en/api/venues/list-venues.md)
- [List agenda sessions](https://docs.orriven.com/en/api/program/list-agenda-sessions.md)
- [List speakers](https://docs.orriven.com/en/api/program/list-speakers.md)

## OpenAPI Specs

- [openapi](https://docs.orriven.com/api-reference/openapi.json)