TicketOpus

Support

Get help with TicketOpus

Start with the product and industry guides or the API reference. When you need a person, email [email protected] or send us your question with a little context about your operation.

Ways to get help

Guides, API docs, and people

Guides

Product and industry guides

Feature guides cover website, booking, payments, operations, events, and reporting; industry guides cover tours, attractions, rentals, studios, camps, private events, and more.

Browse product guides
Developers

API reference

Authentication, scopes, endpoints, examples, and error codes for the External API. Each business creates its own API keys in Admin.

View API documentation

Find your answer

Start with the guide for the job you are doing.

  • Feature guides for each part of the product
  • Industry guides with setup checklists
  • Migration planning for switching platforms

For developers

Build against a documented API.

  • Authentication and scopes
  • Endpoint reference and examples
  • Error codes and retry guidance

Questions before launch

Straight answers before you decide.

Can TicketOpus start with one workflow?

Yes. The platform is designed so an operator can begin with direct booking or another priority workflow and add connected capabilities as the operation matures.

Does TicketOpus support an existing website?

Yes. Add the booking widget to your current site, or build a new site with the TicketOpus website builder.

How should we evaluate a migration?

Start with future bookings, catalog and schedules, customer records, payments and balances, integrations, domains, reporting, and the staff workflows that must work on launch day.

Are all integrations live today?

No. Stripe payments, the External API, webhooks, and SCIM directory sync are live. QuickBooks, Xero, OTA marketplaces, and Google Things to Do are not connected yet, so check with us about any connection your launch depends on.