Get the presence report (night register).

Returns the guests present per night, as one entry per day in date order. Only guests who are actually checked in are counted, split per age group; group on reservationNumber to ignore the age groups. A guest counts from the check-in day up to but not including the registered check-out day, and a stay without a registered check-out keeps counting, so a forgotten check-out keeps that guest in the register every night after. Days run from midnight UTC, so a check-in or check-out registered just after local midnight can land on the neighbouring day. Paging is on reservations, so a stay is never split across pages and X-Total-Count is the number of reservations. Every page repeats all days in the range and fills them with the reservations of that page only, so the days must be merged across pages: an empty items array on a single page does not mean nobody was present. Once every page is merged, a day with nobody present keeps an empty items array, so “nobody there” differs from “not delivered”.

GETRequest

import { RecranetApiClient } from "@recranet/sdk";

const client = new RecranetApiClient({ apiKey: process.env.RECRANET_API_KEY! });

const result = await client.reports.presence({
  dateFrom: new Date("2026-06-01"),
});

Responses

200400429

Response 200

Successful operation

application/json

Example responseGenerated from schema

[
  {
    "date": "2025-10-01",
    "items": [
      {
        "reservationId": 84213,
        "reservationNumber": "2025-1043",
        "reservationName": "Jansen",
        "reservationAccommodationTitle": "Comfort chalet 4p",
        "reservationAccommodationUnitNumber": "B12",
        "reservationDateFrom": "2025-09-29",
        "reservationDateTo": "2025-10-05",
        "ageGroupSpecificationDescription": "Volwassenen",
        "numOfPersons": 2,
        "guestLocality": "Utrecht",
        "guestCountry": "NL",
        "guestDocumentType": "id-card",
        "modified": "2025-09-29T14:03:11+02:00"
      }
    ]
  }
]

Response 400

Bad request

application/json

Example 1

{
  "statusCode": 400,
  "description": "Bad request",
  "errors": [
    "Bad request"
  ]
}

Response 429

Too many requests

application/json

Example 1

{
  "statusCode": 429,
  "description": "Too many requests",
  "errors": [
    "Too many requests"
  ]
}

Query parameters

• dateFromstringrequired
• dateTostringoptional
• groupedbooleanoptional
  Default: false
• includeCancelledbooleanoptional
  Default: false
• accommodationCategorynumberoptional
• offsetnumberoptional
  Default: 0
• limitnumberoptional
  Default: 25

Returns

Array of object

Schema shown for 200 · application/json

• datestringoptional
• itemsobject[]optional
  Show array — 13 properties

  • reservationIdnumberoptional
  • reservationNumberstringoptional
  • reservationNamestringoptional
  • reservationAccommodationTitlestringoptional
  • reservationAccommodationUnitNumberstringoptional
  • reservationDateFromstringoptional
  • reservationDateTostringoptional
  • ageGroupSpecificationDescriptionstringoptional
  • numOfPersonsnumberoptional
  • guestLocalitystringoptional
  • guestCountrystringoptional
  • guestDocumentTypestringoptional
  • modifiedstringoptional

    The reservation timestamp. It also moves for edits unrelated to the register, so it helps spot changes but is not a change filter.