KennelBooker API

Your booking data, wherever you need it

The KennelBooker REST API lets your own applications read the bookings, customers and pets in your account - so you can build the dashboard, report or integration your business actually wants, instead of exporting spreadsheets by hand.

Read the documentation See what's available

REST · JSON responses · API-key authentication

Your first request 
curl --request GET \
  --url "https://api.kennelbooker.com/api/v1/bookings" \
  --header "X-Api-Key: kb_live_your_api_key" \
  --header "Accept: application/json"

What you can build with it

If you can read your bookings programmatically, a lot of manual work disappears.

Your own reporting dashboards

Pull bookings into Power BI, Google Sheets or an internal dashboard and slice occupancy, revenue and booking mix exactly how your business measures it.

Marketing that knows your customers

Sync customer records into your CRM or email platform, and segment on real behaviour - who boarded last summer, who has not visited in six months.

Website & app integrations

Surface today's arrivals on your own site, feed a whiteboard display in reception, or drive an internal staff app from live booking data.

Automated exports and backups

Schedule a nightly pull of customers, pets and bookings into your own data store - no more clicking export every month.

Multi-site roll-ups

Running more than one KennelBooker business? Use each business's key to bring every site's numbers together in one view.

Compliance record-keeping

Pull booking and pet records into your own archive to support licensing and record-retention requirements alongside KennelBooker's own backups.

New

Ask your kennel a question

You do not have to write code to get something out of your data. Connect KennelBooker to Claude, or any assistant that speaks the Model Context Protocol, and just ask.

“Who is arriving tomorrow?”

The full arrivals list, with rooms, pets and owner contact details, without opening the diary.

“Does Poppy need medication?”

Feeding times, medication rounds, allergies and vet notes, pulled straight from the pet's record.

“What is still unpaid this month?”

Ask across any date range, booking type or status, and get the answer in a sentence rather than a report.

It can look, not touch

The connection is read-only. An assistant can answer questions about your diary but cannot create, change or cancel a booking.

Nothing to install

Download one file, drag it into Claude, paste your API key. About a minute, and no developer required.

Your key stays with you

It runs on your own computer using your own key. We host nothing and hold nothing on your behalf.

See how to set it up

Three steps to your first request

No OAuth dance, no SDK to install. A key and a header.

1

Create an API key

Generate a key in the Developer API area of your KennelBooker business account. Each key belongs to one business and unlocks only that business's data.

2

Send it in the header

Add your key to the X-Api-Key header on every request - never in the URL or query string.

3

Use the JSON

Read the JSON response and connect KennelBooker data straight into your application, report or workflow.

Response envelope - every collection endpoint returns the same shape
{
  "page": 1,
  "pageSize": 5,
  "totalRecords": 151,
  "totalPages": 31,
  "items": [
    {
      "bookingId": 229,
      "bookingType": "boarding",
      "reference": "KB000229",
      "status": "new",
      "customerId": 165,
      "customerName": "Example Customer",
      "petNames": "Milo",
      "numberOfPets": 1,
      "checkInDate": "2026-05-07T00:00:00Z",
      "checkOutDate": "2026-05-08T00:00:00Z",
      "bookingPaid": false
    }
  ]
}

What's available

Three resources, all returning paginated JSON from https://api.kennelbooker.com/api/v1

Bookings

Booking records with dates, statuses, booking type, service, pet names and payment flags.

  • GET List bookings
  • GET Get booking by ID
  • GET Get booking by reference

Filter by date range, booking type, status, customer, service or free-text search.

Customers

Customer profiles and contact information, plus their pets and their booking history.

  • GET List customers
  • GET Get a customer
  • GET List customer pets
  • GET List customer bookings

Filter by created or updated date, archived state, or free-text search.

Pets

Pet profiles including species, breed, owner relationship and important details.

  • GET List pets
  • GET Get a pet

Filter by customer, species, breed or free-text search.

Browse the full API reference

Built to be boring - in a good way

Predictable conventions, so your integration behaves the same on day one and day four hundred.

REST over HTTPS

Standard GET requests, standard status codes, JSON in and out. Nothing proprietary to learn.

Consistent pagination

Every collection returns page, pageSize, totalRecords, totalPages and items - so paging logic is written once.

Real filtering

Narrow results server-side by date range, type, status, customer, service, species or breed before a single record crosses the wire.

ISO 8601 dates

Send and receive timestamps with explicit timezones, so a UK kennel and a US integration agree on what "Tuesday" means.

Copy-paste examples

Every endpoint in the docs ships with working cURL, C# and JavaScript samples.

Per-business API keys

A key maps to exactly one KennelBooker business and reaches only that business's data.

Clear failure modes

A missing, malformed or revoked key returns 401 Unauthorized - no silent empty responses to debug.

Read-only today

The v1 API reads your data; it cannot alter or delete it. An integration bug can't damage your live bookings.

Keys that stay yours

An API key grants access to your business data, so it deserves the same care as a password. The rules are short.

Read the authentication guide

Keep keys server-side

Only call the API from infrastructure you control. Never place a key in browser JavaScript, a public repository or a mobile app.

Use secure configuration

Store keys in environment variables or an encrypted secret store - not in source control.

Never log a key

Redact the X-Api-Key header from application logs and error reports.

Replace exposed keys

Treat any accidentally disclosed key as compromised and issue a replacement straight away.

Frequently asked questions

Does KennelBooker have an API?

Yes. KennelBooker provides a REST API that returns JSON, letting you read your bookings, customers and pets from your own applications. Requests are authenticated with an API key sent in the X-Api-Key header, and the base URL is https://api.kennelbooker.com/api/v1.

How do I get a KennelBooker API key?

Create or copy your key from the Developer API area of your KennelBooker business account. Each key is tied to a single business and only grants access to that business's data, so if you connect more than one KennelBooker business you store a separate key for each.

What data can I access through the KennelBooker API?

Three resources are available: bookings (including dates, statuses, booking type, service and payment flags), customers (profiles and contact information, plus their pets and bookings) and pets (profiles, species, breed and their owner relationship).

Does the KennelBooker API cost extra?

The API and its documentation are available to KennelBooker customers. Speak to our team if you are planning a larger integration and we will help you scope it.

Can I connect KennelBooker to Claude or another AI assistant?

Yes. KennelBooker publishes a free Model Context Protocol (MCP) server that connects your account to Claude and other AI assistants, so you can ask about your bookings, customers and pets in plain English. It installs in about a minute, runs on your own computer with your own API key, and is read-only, so an assistant can look things up but cannot change or cancel a booking.

Is the KennelBooker API secure?

Every request must carry a valid API key in the X-Api-Key header, sent over HTTPS. Keys are per-business and should only ever be used from server-side code you control - never from browser JavaScript or a mobile app. Missing or invalid keys receive a 401 Unauthorized response.

Start building

Full documentation, request contracts and working code samples are waiting on the developer portal.

Open the developer portal Start your free trial