Endpoints
The OpenAPI 3.1 spec is the source of truth — fetch it from
/api/v1/openapi.json
or as YAML at /api/v1/openapi.yaml.
Reference summary
| Method | Path | Scope | Description |
|---|---|---|---|
GET | /me | — (any key) | Account info + key metadata |
GET | /customers | customers:read | List customers (optional ?q= search) |
GET | /customers/{id} | customers:read | Get a customer by id |
GET | /pets | pets:read | List pets (optional ?customerId= filter) |
GET | /pets/{id} | pets:read | Get a pet by id |
GET | /bookings | bookings:read | List top-level bookings |
GET | /bookings/{id} | bookings:read | Get a booking by id |
POST | /bookings | bookings:write | Create boarding or grooming booking |
PATCH | /bookings/{id} | bookings:write | Update booking status |
GET | /services | services:read | List services catalogue |
GET | /payments | payments:read | List most-recent 200 payments |
GET | /payments/{id} | payments:read | Get a payment by id |
Money + timestamps
- All monetary amounts are integers in the account's currency's minor units
(pence / cents). E.g. £42.50 =
4250. - All timestamps are UTC ISO 8601 strings (e.g.
2026-06-01T10:00:00.000Z).
Pagination
Endpoints return up to 200 rows. Cursor pagination will be added in a future version; today the listing endpoints are sufficient for the supported integration use-cases.
Creating a booking
Boarding example:
curl -X POST https://app.kennels.app/api/v1/bookings \
-H "Authorization: Bearer kennel_pk_live_..." \
-H "Content-Type: application/json" \
-d '{
"type": "boarding",
"facilityId": "01HTZ...",
"customerId": "01HTZ...",
"petId": "01HTZ...",
"checkIn": "2026-06-01T10:00:00Z",
"checkout": "2026-06-05T10:00:00Z"
}' Grooming example:
{
"type": "grooming",
"facilityId": "01HTZ...",
"customerId": "01HTZ...",
"petId": "01HTZ...",
"startAt": "2026-06-01T13:00:00Z",
"durationMin": 90,
"serviceIds": ["01HTZ..."]
} Fetch Public API · OpenAPI 3.1 spec at
/api/v1/openapi.json