Documentation
Everything you need, in one place
Guides for organizers, selfhost installation, SaaS operations, and the REST API.
/
Start here
From nothing to a live calendar
- 1 Create a schedule Pick Talent, Venue or Curator, name it to get your URL, and add a logo and colors. Read guide
- 2 Add your events Type them in or paste a listing for AI to parse. Sell tickets through Stripe, PayPal or another payment method, free up to 25 paid tickets a month. Read guide
- 3 Share it Embed the calendar on your site, post the link, and collect subscribers who hear about new events on their own. Read guide
User Guide
Every part of the product
Set up
Create an account, a schedule, and make it yours. 3 guidesEvents
Add events by hand, from text, or from a photo. 3 guidesSell
Take money for tickets, passes and bookings. 5 guides-
Selling Tickets
Set up ticketing and manage sales. -
Subscriptions & Passes
Sell one pass a guest reuses across many events. -
Allocated Seating
Sell reserved seats from a plan of your venue. -
Gift Cards
Sell prepaid gift cards buyers send to someone else. -
Appointments
Let guests book a time with you on a public page.
Promote
Get your events in front of an audience. 4 guidesManage
Run the day to day and see how it is going. 4 guidesRun it yourself
Platform and developer docs
-
Self-managed
Selfhost Installation
Run Event Schedule on your own server. A selfhosted install resolves to Enterprise, so no plan gate applies. Requirements and installation Stripe payments and calendar sync Email, AI and boost setup Admin panel, federation, accessibility View selfhost docs -
Multi-tenant
SaaS Platform
Run Event Schedule as a multi-tenant SaaS with subdomains, plans and per-tenant custom domains. Multi-tenant setup Custom domains with automatic SSL Twilio phone verification Federation, ads and promotions View SaaS docs -
REST API
Developer
Drive Event Schedule from your own code over REST. API access is a Pro feature, on reads as well as writes. REST API reference API keys and rate limits HMAC-signed webhooks Sale, event and check-in payloads Explore the API
Reference
Glossary
Key terms used throughout Event Schedule.
- Schedule
- Your event calendar, with its own URL, branding and settings. One schedule holds as many events as you like, on every plan.
- Schedule type
- Talent, Venue or Curator. The type decides what a schedule gets: a venue has a full address, a curator aggregates events from other schedules. Choose carefully, because the type is fixed once the schedule is saved.
- Sub-schedule
- A category for events inside one schedule, such as Live Music, Comedy or Workshops. Each one has its own color and its own URL, and visitors can filter by it. It organizes and color-codes only: it cannot hide an event.
- Event
- A single occurrence with a date, time, location and details. An event belongs to a schedule and can repeat daily, weekly, every few weeks, monthly or yearly, with dates you add or skip.
- Request
- An event waiting for your approval: one a visitor submitted from your public request page, or one another schedule added you to. Requests sit on the Requests tab until you accept or decline them, and you can opt in to an email when new ones land.
- Unclaimed page
- A schedule page created for a performer or venue you name on an event before they are on Event Schedule. It says who created it, credits each date to the schedule that added it, and stays out of search engines. The person it names claims it with an account on the email address or phone number it lists, and becomes its owner.
- Ticket
- A ticket type on an event, such as General or VIP. Buyers pay through your own Stripe or PayPal account (or Payfast, Invoice Ninja, a payment link or cash), with no platform fees on any plan. Free schedules sell up to 25 paid tickets a month; Pro removes the cap.
- RSVP
- Free sign-up for an event, with an optional capacity limit per date. Available on every plan, and no payment account is needed.
- Follower
- Someone with an account who follows your schedule, which shares their name and email with you. Pressing Follow on its own reaches an account follower only through a newsletter you send; the automatic digest goes to people who asked for email updates (see Subscriber).
- Subscriber
- Someone who asked your schedule for email updates: from the sign-up panel on your page, with their name and email, confirmed from the link we send, or from a tick box when they buy a ticket or register. Confirming the sign-up panel also sets up an account for them wherever sign-up is open. Subscribers get a digest automatically when you publish events your schedule created, at most one every few days, and it does not draw on the newsletter allowance.
- Interest list
- The email addresses left on one event with "Tell me when tickets go on sale", or "Tell me if anything changes" once it is selling. No account and no name. They hear about that date only: when tickets go on sale, a reminder before it starts, a notice if it is cancelled, and any notice you choose to send if the date or venue changes. It is not a subscription to your schedule.
- Newsletter
- An email you write and send to a segment. The monthly allowance counts recipients rather than sends: 10 free, 100 on Pro, 1,000 on Enterprise, and unlimited on selfhost or with your own mail server.
- Segment
- A saved audience for newsletters: all followers, ticket buyers, a ticket waitlist, buyers from one sub-schedule, or a list you enter by hand.
- Embed
- Your schedule shown on another website inside an iframe. The calendar embed and the RSVP form are free; embedding the ticket purchase widget needs Pro.
- Admin Panel
- The management side of one schedule, where you add events, change settings and read your analytics. Not the selfhost admin panel at /admin, which manages a whole install.
100% open source
Event Schedule is fully open source. Explore the code, report an issue, or contribute on GitHub.