Apps and Integrations

Booking Phoenix talks to a small set of third-party services for things outside its core scope — payment processing, email delivery, real-time updates, accounting handoffs, marketing tools. This guide covers the integrations available, what they're for, and how to connect each one.

Where to find integrations

Two pages, depending on what you're connecting:

• Settings → Integrations — tenant-wide service connections (Stripe, SMS provider, mail provider, etc.).
• Settings → Apps — opt-in feature toggles and add-on apps you can enable per branch.

Stripe (payment provider)

The most important integration. Stripe is how you take card payments — on the booking widget, at the POS, on the voucher purchase form, for refunds. Without Stripe connected, you can only take cash / EFTPOS recorded manually.

See Setting Up Stripe for the full walkthrough.

SMS providers

If your tenant has SMS enabled, you'll be configured with one of the supported providers (varies by region — Twilio, MessageBird, ClickSend, others). The integration page shows your provider, credit balance, and a test-send button.

Topping up SMS credits is done through the provider's billing, not Booking Phoenix. The integration page links through to your provider's dashboard.

Pusher (real-time updates)

Pusher is what makes the calendar update live without refreshing — when a booking comes in, every staff member's screen shows it within a second. This is configured by us during tenant setup; you don't usually touch it. If real-time updates stop working, raise a support ticket.

Sentry (error tracking)

Internal use — Sentry collects error reports so we can fix bugs before customers report them. There's nothing for you to configure.

SendGrid / mail provider

Booking Phoenix sends transactional email through SendGrid by default. For high-volume tenants or those wanting branded sending domains, we can configure a custom mail-provider account (your own SendGrid, Postmark, AWS SES). See Email Deliverability for the setup walkthrough.

Accounting handoffs

If you want bookings, payments, and refunds to flow into your accounting software automatically, two paths:

• CSV exports — export from Reports → Daily Revenue / Refunds and import into your accounting tool. Manual but works with any system.
• API integration — for tenants on plans that include API access, we can pipe payment data into Xero, MYOB, QuickBooks, or similar. Talk to support for setup.

Calendar exports

Bookings can be subscribed to from external calendars (Google Calendar, Apple Calendar, Outlook) via an iCal feed. Each user has a personal subscription URL on their profile — copy it into your calendar app's "Subscribe to calendar" feature, and your bookings appear alongside personal events.

The iCal feed is read-only — changes in your external calendar don't sync back. For two-way sync, use the API.

Webhooks

For technical integrations, Booking Phoenix can fire HTTP webhooks on key events — booking created, booking cancelled, payment received, customer created. Configure these on the API tab of the integrations page (only available on plans with API access).

Common uses:

• Pipe new bookings into your CRM or marketing tool.
• Trigger external workflows (e.g. send to Slack when a high-value booking comes in).
• Sync customers to your email marketing platform.

Webhook setup requires a developer on your end — we provide the event docs and you build the receiver.

Marketing tools

For email marketing beyond Booking Phoenix's built-in bulk send, common patterns:

• Export the customer list (filtered by marketing consent) and import into Mailchimp, Klaviyo, ConvertKit, or similar.
• Set up a webhook so new customers auto-sync into your marketing platform.
• Use the API to keep both systems in sync continuously.

For the heaviest setups — e.g. behavioural triggers based on bookings — the API is the right tool. CSV import suffices for most venues.

Apps you can enable

The Apps page (Settings → Apps) shows feature toggles your tenant has opted into:

• Surveys — post-booking feedback. See Collecting Feedback with Surveys.
• SMS — transactional and bulk SMS. See Sending SMS to Customers.
• Vouchers — gift voucher purchase, redemption, custom designs. See Creating a Gift Voucher.
• Discounts — coupon codes. See Creating a Discount Code.
• Leaderboards — public score / time leaderboards per room.
• Loyalty — points / rewards programmes (where available).

Toggling an app on doesn't bill anything extra unless the app has its own usage-based pricing (SMS in particular). Check the app's tile for the pricing model before enabling.

Security and credentials

• API keys, webhook secrets, and integration credentials are tenant-scoped — only users with the Integrations permission can view or change them.
• Rotate API keys at least annually, and immediately if you suspect a leak.
• Webhook receivers should verify request signatures so they only act on real Booking Phoenix events, not forged ones.

Common pitfalls

• Mixed test and live keys. Stripe (and some others) have separate test and live keys. Mixing them in the same branch will fail to charge, fail to refund, or charge the wrong account. Keep test setups on a separate non-production branch.
• Stale credentials. Integrations occasionally break because the third-party rotated their API or revoked your token. Check the integrations page periodically — "Connected" should be green.
• API key in front-end code. Never paste a secret API key into HTML or JavaScript on your website — it'll be visible to anyone who views the source. Secret keys live on your servers; widget snippets only contain public tokens.

Asking for new integrations

If you need an integration that's not in the list, raise a support ticket. We track demand for new integrations and prioritise based on what's asked for most often. For one-off custom integrations on enterprise plans, we can sometimes build directly.