Checkfront API

Name: Checkfront API API
Brand: Checkfront API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementoauth212 EndpointsREST

For Agents

Create and update bookings, look up items and customers, and run check-in or check-out flows in Checkfront so an agent can manage the reservations side of a tour, rental, or event business.

Quickstart

Get started with Checkfront API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a booking"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Checkfront API API.

Create new bookings with selected items, customer details, and dates

Update existing bookings to change dates, items, or customer info

Run check-in and check-out flows on confirmed bookings

List bookable items, categories, and scheduled events for availability

Read customer records to power loyalty or CRM integrations

GET STARTED

Start building with Checkfront API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Checkfront API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Checkfront API, keeping it validated and agent-ready. Checkfront is a booking management platform used by tour operators, accommodation providers, equipment renters, and event organisers to take reservations online and run the operations behind them. The v3.0 REST API exposes 12 endpoints for managing bookings, bookable items, categories, customers, and events, including check-in and check-out flows. It is well suited to teams building portals, self-service kiosks, or backend integrations on top of Checkfront.

Use Cases

Patterns agents use Checkfront API API for, with concrete tasks.

★ Self-Service Booking Portal

Build a custom booking portal that lists available items by category, lets customers pick dates, and creates a Checkfront booking. The portal calls /item and /category to render availability, /booking/create to confirm a reservation, and /booking/{booking_id} to fetch confirmation details. Useful for operators who want a branded checkout outside the standard Checkfront widgets.

Create a booking via /booking/create with item_id 42, start_date 2026-07-15, end_date 2026-07-16, and customer email guest@example.com.

Check-In Kiosk

Run a tablet-based kiosk at the venue that lets staff (or guests) check in an existing booking on arrival. The kiosk searches /booking by date or customer, displays the result, and calls /booking/{booking_id}/checkin to mark them as arrived. /booking/{booking_id}/checkout handles the return flow.

Find today's bookings via GET /booking, then call POST /booking/{booking_id}/checkin for booking_id 9876.

Booking Sync with External Systems

Mirror Checkfront bookings into a finance system, CRM, or operations dashboard. List bookings on a schedule, transform the records, and push them downstream. Useful when Checkfront is the source of truth for revenue but other systems need the same data for accounting and reporting.

Pull all bookings from /booking created in the last 24 hours and return their booking_id and total.

AI Agent for Booking Management

An autonomous agent receives natural-language booking requests, picks the right item, and creates the Checkfront booking — all through Jentic. The agent never holds the OAuth access token in its prompt; Jentic injects it at execution time and returns the booking confirmation.

Through Jentic, search 'create a booking', load the schema for /booking/create, and execute with item_id 42 and the requested dates.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for checkfront api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/booking/create

Create a booking

GET

/booking

List bookings

GET

/booking/{booking_id}

Fetch a booking

POST

/booking/{booking_id}/checkin

Check in a booking

POST

/booking/{booking_id}/checkout

Check out a booking

GET

/item

List bookable items

GET

/category

List categories

POST

/booking/create

Create a booking

GET

/booking

List bookings

GET

/booking/{booking_id}

Fetch a booking

POST

/booking/{booking_id}/checkin

Check in a booking

POST

/booking/{booking_id}/checkout

Check out a booking

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Checkfront OAuth 2.0 access and refresh tokens are stored encrypted in the Jentic MAXsystem vault. Jentic injects the bearer token at execution time and refreshes it automatically — agents never see the raw credentials.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a booking' or 'check in a guest') and Jentic returns the matching Checkfront operation with its input schema, so the agent picks among 12 endpoints without browsing docs.

Time to first call

Direct Checkfront integration: 2-3 days for OAuth setup, booking lifecycle, and check-in flow. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Checkin.no API

Hospitality check-in platform with a different focus on guest registration

Choose Checkin.no when the need is regulatory guest registration; Checkfront is for full booking management

Complementary

Cheddar Up API

Group payments and collections platform that can take payments alongside Checkfront bookings

Choose Cheddar Up when collecting group fees outside a formal booking flow

Complementary

Checkly API

Synthetic monitoring you can use to verify Checkfront booking endpoints stay healthy

Choose Checkly to set up uptime monitoring against your Checkfront subdomain

FAQs

Specific to using Checkfront API API through Jentic.

Why is there no official OpenAPI spec for Checkfront API?

Checkfront does not publish an OpenAPI specification on its developer site. Jentic generates and maintains this spec so that AI agents and developers can call Checkfront API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Checkfront API use?

The Checkfront API uses OAuth 2.0 with the authorization code flow. Authorization happens at https://{subdomain}.checkfront.com/oauth and tokens are issued at /oauth/token. Through Jentic, OAuth tokens are stored encrypted in the MAXsystem vault and refreshed automatically, so agents never see the raw access token.

Can I create a booking with the Checkfront API?

Yes. POST /booking/create accepts the bookable item, dates, customer details, and any extras and returns the new booking_id. You can then update it with POST /booking/{booking_id}/update or run check-in via POST /booking/{booking_id}/checkin.

How do I check in a guest with the Checkfront API?

Call POST /booking/{booking_id}/checkin to mark a booking as checked in. Use POST /booking/{booking_id}/checkout for the return flow. Both endpoints update the booking's status and return the resulting record.

What are the rate limits for the Checkfront API?

The OpenAPI specification does not declare formal rate limits. Checkfront enforces per-account throttling on its production servers — plan for retry-with-backoff on 429 responses and avoid polling /booking aggressively.

How do I create a Checkfront booking through Jentic?

Install the SDK with `pip install jentic`, then call Jentic.search('create a booking'), load the schema for /booking/create, and execute with the item_id, dates, and customer details. Jentic handles the OAuth token exchange and refresh.