The Kinapi API
Automate traveller registration for your bookings: a REST API to create check-ins, follow their status and retrieve contracts and reports filed with SES Hospedajes.
How it works
The model is deliberately simple: your software creates one check-in per booking and gets a URL back. You send that URL to the guest (by email, WhatsApp or your own channel) and everything else happens inside Kinapi: each guest fills in their details (validated against the SES rules), signs the contract, and on the night of arrival the traveller report is filed automatically with SES Hospedajes.
Your integration can be as small as a single call (create check-in) or follow the whole thing: read the registered guests, download the signed contract and verify the Ministry’s confirmations.
Base URL
https://api.kinapi.es/api/v1
Every request goes over HTTPS and uses JSON in the body and the response. Authentication is by API key — see Authentication.
OpenAPI specification
The whole API is described in an OpenAPI 3.0 file generated from the very schemas that validate each request, so it cannot lag behind the code. Use it to generate a client in your language (openapi-generator, openapi-typescript…), import it into Postman or Insomnia, or try the API from the browser in Swagger UI.
https://www.kinapi.es/openapi.json
In Postman: Import → Link and paste the URL. Every operation comes with its body, responses and error codes; you only need to set your API key in the ocp-apim-subscription-key header.
Your first call, in 30 seconds
curl -X POST https://api.kinapi.es/api/v1/checkins \
-H "ocp-apim-subscription-key: YOUR_API_KEY" \
-H "content-type: application/json" \
-d '{
"reservationId": "R-2026-0412",
"listingId": "38291",
"confirmationCode": "HMXK4L",
"checkInDate": "2026-08-14",
"checkOutDate": "2026-08-18",
"numGuests": 4
}'{
"reservationId": "R-2026-0412",
"status": "pending",
"url": "https://checkinsas…/c/aGb3xKf9…",
"created": true
}Resources
Check-ins
Create, list, read, update and cancel the check-in for each booking.
Guests
Register travellers from your own system, read them back and see their signature status.
Properties
Create and manage accommodations and their SES establishment codes.
Owners
The people behind the accommodations: the tax details that appear on the contract.
Contracts
Configure what the contract says with templates, and download the signed PDF and the traveller report.
SES Hospedajes
Status of the traveller report, immediate filing and the official code tables.
SES credentials
One set per lessor, assignable per property, with a connection test.
Billing
This month’s usage, estimated cost and the month-by-month history.
Webhooks
Get notified in your own system when something happens, with a verifiable signature.
Account settings
Settings, white-labelling of the guest form and webhook management over the API.
Exports and offboarding
One owner’s records or the whole account’s in a ZIP, offboarding an owner and closing the account.
Would you rather an agent used it than write the client yourself?
kinapi-mcp-server exposes this same API as MCP tools: Claude (or any compatible agent) creates check-ins, reads their status and downloads contracts by talking straight to Kinapi, without you writing an HTTP client for it.