The Late Check-in Notifications module helps operations teams identify guests who are expected to arrive after the company’s configured cut-off time (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/sdurutr436/stay-sidekick/llms.txt
Use this file to discover all available pages before exploring further.
hora_corte). Guest data uploaded via XLSX is processed entirely in memory and is never written to the database — in compliance with GDPR principles. Notification templates are stored per-company under the CHECKIN_TARDIO vault category and can be reused across sessions.
All endpoints require
Authorization: Bearer <token>. POST requests also require the X-CSRF-Token header.GET /api/notificaciones/checkin-tardio/status
Returns the current operational status: whether a PMS is connected, how many check-ins are expected today (or on the given date), the number of active apartments, and the configured late cut-off time. Auth required: Yes | Role: anyQuery Parameters
Date to check in
YYYY-MM-DD format. Defaults to today if omitted.Response
trueWhether a PMS integration is configured for the company.
Number of check-ins expected on the requested date (sourced from PMS when connected).
Number of active apartments in the company’s catalog.
Late check-in cut-off time in
HH:MM format (24h). Check-ins after this time are flagged as late.Example
POST /api/notificaciones/checkin-tardio/checkins
Accepts an XLSX file, parses each row against the company’s cut-off time, and returns only the guests whose arrival time is afterhora_corte. No data is saved.
Auth required: Yes | Role: anyRate limit: 20 requests / hour
The cut-off time and column configuration used for parsing are read from the company’s notification config (
GET /api/perfil/notificaciones-tardio-config). Make sure the XLSX column mapping is configured before uploading.Request
Multipart form upload:The
.xlsx file containing the day’s check-in list. Must have a .xlsx extension and must not be empty.Response
trueList of guests with a late expected arrival.
Optional. Row-level parsing warnings (e.g., unrecognised time formats, missing columns).
Example
GET /api/notificaciones/checkin-tardio/plantillas
Lists all active notification templates for theCHECKIN_TARDIO category that belong to the authenticated user’s company, ordered by creation date ascending.
Auth required: Yes | Role: any
Response
trueArray of template objects.
Example
POST /api/notificaciones/checkin-tardio/plantillas
Creates a new notification template in theCHECKIN_TARDIO category. The template is created with idioma = "es" and is immediately available for use.
Auth required: Yes | Role: any
Request
Template display name. Must not be empty.
Template body text. Must not be empty. Supports free-form text; placeholder syntax is defined by the front-end convention.
Response
201 Created
trueThe newly created template object (id, nombre, contenido).
Example
PUT /api/notificaciones/checkin-tardio/plantillas/<id>
Updates the display name and body of an existingCHECKIN_TARDIO template. Both nombre and contenido are required.
Auth required: Yes | Role: any
Path Parameters
UUID of the template to update.
Request
New template display name. Must not be empty.
New template body text. Must not be empty.
Response
trueThe updated template object (id, nombre, contenido).
Errors
404 Not Found — template not found or belongs to another company.
Example
DELETE /api/notificaciones/checkin-tardio/plantillas/<id>
Permanently removes aCHECKIN_TARDIO notification template. This action cannot be undone.
Auth required: Yes | Role: any
Path Parameters
UUID of the template to delete.
Response
200 OK — {"ok": true}
404 Not Found — template not found or belongs to another company.

