Stripe payments
Card payments, refunds, and payouts run through Stripe. Each business connects its own Stripe account.
See paymentsAPI and webhooks
A documented API, webhooks, and Stripe payments
Payments run on Stripe. Your own systems and approved partners can read your catalog and availability, create bookings, and receive webhook events through a documented, company-scoped API, and your identity provider can keep your staff directory in step through SCIM.
What connects today
Live now, and what is still to come
External API and webhooks
Read catalog and availability, create and change bookings, and check guests in through a documented API with scoped keys. Webhooks tell your systems when something changes, and SCIM lets your identity provider end a leaver's access.
Read the API referenceAccounting and channel connections
QuickBooks, Xero, OTA marketplaces, and Google Things to Do are not connected yet. Until then, export accounting records as CSV, and tell us which connection you need.
Tell us what you needPayments and exports
Get paid through Stripe and hand clean records to your accountant.
- Stripe card payments, refunds, and payouts
- Accounting exports as CSV
- Payment and payout reports
Developer access
Give partners and your own systems a documented API.
- Public API reference with examples
- Keys scoped to exactly what each partner needs
- Request logs and webhook delivery history
Connecting through the API
From API key to live connection
-
01
Create an API client
Add a client in Admin for each system or partner that needs access.
-
02
Grant only the scopes it needs
Choose read or write access for catalog, bookings, check-in, and more.
-
03
Test with a dry run
Validate bookings before creating real ones.
-
04
Watch the logs
Review request logs and webhook deliveries once the connection is live.
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.