← Back to all docs

Checkfront API

Checkfront is an online booking platform that helps tours, activities, rentals, and accommodation businesses manage reservations, availability, resources, payments, and customer communications. Its API lets you programmatically pull bookings, items, availability, customers, and account data—and push updates like new bookings, check-ins, notes, and status changes back into Checkfront.

By Alex KlarfeldMay 30, 2026
Checkfront API

What is Checkfront?

Checkfront is an online booking software platform that enables tours, activities, rentals, and accommodation businesses to manage reservations, resources, payments, and customer communications. Operators use Checkfront to sell experiences as daily, multi-day, timeslot, or flexible booking types, automate administrative overhead, manage assets across multiple experiences, and expand reach through integrations with online travel agencies.

Core product areas include:

  • Real-time availability calendars and resource management automation
  • Email and SMS notifications and digital waivers
  • Payment processing, including deposits and buy-now-pay-later options
  • Seasonal pricing and discount management
  • Ticketing and scanner check-in functionality
  • Booking channel integrations with OTAs such as GetYourGuide and MyAllocator

Common data entities:

  • Bookings, Booking Sessions, Statuses, Invoices, Check-ins
  • Items, Categories, Availability, Rates, Packages
  • Customers, Notes, Forms, Waivers
  • Payments, Refunds, Deposits, Discounts
  • Account, Company, Events, Calendar Edits

The Checkfront Integration Challenge

Operators run their entire booking business on Checkfront daily, but turning its booking workflows into reliable API-driven automation has real friction:

  • API access is gated: trial accounts cannot use the API, and developer access must be requested through Checkfront before token pairs are issued
  • Versioning risk: the v3.0 API is in maintenance mode and slated to be replaced by V4, so integrations must absorb migration churn
  • Public vs. authenticated split: booking/session and booking/create only work when the Public API is enabled, while management endpoints require authenticated token-pair or OAuth2 access
  • Per-account configuration: items, categories, rates, and booking forms are customized per operator, so generic integrations break across accounts
  • Availability and rate complexity: real-time calendars, seasonal pricing, and multiple booking types make availability and pricing data non-trivial to model
  • Webhook handling: booking status changes, calendar edits, and payment/refund events need careful subscription and replay handling to stay in sync

How Supergood Creates Checkfront APIs

Supergood reverse-engineers authenticated Checkfront flows alongside the published v3.0 API to deliver a resilient, normalized API layer for your account—so you integrate once and stay stable across version and configuration changes.

  • Handles token-pair and OAuth2 authentication, including staff-account login, securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes bookings, items, availability, and customers into consistent objects across accounts
  • Tracks v3.0-to-V4 changes and account-specific configuration drift so your integration keeps working

Use Checkfront with AI agents: Checkfront MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your booking types, items, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready Checkfront adapter tailored to your account configuration and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Checkfront evolves.

checkfront

API Endpoints

Authentication

POST/authenticate

Authenticate to a Checkfront account using token-pair or OAuth2 credentials and obtain a session for downstream calls.

Bookings

GET/bookings

List bookings with filters for date range, status, item, and customer, returning order and associated details.

Bookings

POST/create_booking

Create a new booking from a session, mirroring the hosted booking page checkout flow when the Public API is enabled.

Bookings

POST/checkin

Check in or check out an existing booking and update its status, supporting ticketing and scanner workflows.

Inventory

GET/items

Retrieve bookable items, categories, rates, packages, and real-time availability for the account.

Customers

GET/customers

Pull customer records, notes, and form/waiver data associated with bookings.

Use Cases

Sync bookings into a central data warehouse

- Pull bookings, statuses, and invoices across all booking types into a single warehouse - Stream booking status-change and payment events to downstream BI and finance tools - Reconcile customer and waiver records for a unified guest 360

Automate availability and inventory updates

- Read real-time availability, rates, and packages for items and categories - Push seasonal pricing and discount changes without portal clicks - Keep OTA channels in sync with current inventory and rates

Streamline check-in and ticketing

- Trigger check-in and check-out from scanner or kiosk apps - Update booking statuses and capture notes in real time - Route no-shows and late arrivals to operational workflows

Reconcile payments and deposits

- Sync payments, deposits, and refunds into accounting and AR systems - Match discounts and buy-now-pay-later balances against bookings - Surface outstanding balances to follow-up and retention workflows

Technical Specifications

Authentication

Token-pair and OAuth2 (including staff-account login) handled in a managed session

Connectivity

Authenticated flows plus the published Checkfront v3.0 REST API, with public booking endpoints where enabled

Response format

Normalized JSON across bookings, items, availability, customers, and payments

Rate limits

Adaptive throttling tuned to your account to avoid Checkfront-side limits

Session management

Automatic session refresh, token rotation, and credential vaulting

Data freshness

Near real-time pulls for bookings and availability with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for booking modified, status change, calendar edits, and payment/refund events

Latency

Sub-second reads on cached items and availability; multi-second writes when creating bookings

Throughput

Horizontally scaled workers sized to peak seasonal booking volume

Reliability

Retry, backoff, and idempotency keys for booking creation and status changes

Adaptation

Continuous monitoring of the v3.0-to-V4 migration and account-specific configuration drift

Frequently asked questions

Yes. Checkfront restricts API access to paid accounts—trial users cannot access it—and developer credentials must be requested before token pairs are issued. Supergood works with your existing account entitlements and authenticated sessions.

The Checkfront v3.0 API is in maintenance mode and slated to be replaced by V4. Supergood monitors that migration and adapts your integration so it keeps working across the transition without you re-engineering it.

Yes. When the Public API is enabled, booking/session and booking/create reproduce the hosted booking page flow, and Supergood normalizes these so you can build sessions and create bookings through a single consistent surface.

Yes. Items, categories, availability, rates, and packages are exposed through the normalized API, including seasonal pricing and discounts, so you can read and update inventory across booking types.

Booking check-in and check-out and status changes are available through the API, so scanner, kiosk, and ticketing apps can update bookings in real time.

Ready to get a real API?