Reports
VIZA
Check Out

NTAK Check-out event

On this page, we will explore the process of programmatically constructing the VIZA check-out report. We will delve into the steps and techniques required to build the report dynamically through code.

Request

POST/v1/accommodations/{accommodation}/reports/viza/check_out
curl -X POST https://api.ntak.guru/v1/accommodations/99845d23-7ffb-4267-85ef-c8d4ac70e46a/reports/viza/check_out \
  -H "Authorization: Bearer {token}" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"occurredAt":"1986-10-07 13:01:29","guests":[{"id":"c5a366f4-a667-3e83-b691-9074430c20dd","departure":"1984-02-17 07:30:40"}]}'

URL Parameters

NameDescription
accommodationThe accommodation id

Request body

occurredAt

Date of the event.

TypeFormatRequired
stringY-m-d H:i:s UTCYes

guests

The guests who check in to the accommodation. Minimum 1 guest.

TypeRequired
object[]Yes
  • id

    The unique identifier of the guest.
    This ID must be the same as it was in the check in report.

    TypeRequired
    uuidYes
  • departure

    The date and time of the departure of the guest.

    TypeFormatRequired
    stringY-m-d H:i:s UTCYes
{
  "occurredAt": "1986-10-07 13:01:29",
  "guests": [
    {
      "id": "c5a366f4-a667-3e83-b691-9074430c20dd",
      "departure": "1984-02-17 07:30:40"
    }
  ]
}

Response

{
  "message": null,
  "payload": {
    "id": "f2e0ed9f-1d99-471e-ab69-e3967cb07801",
    "messageId": "e3ce35b4-4049-494e-bab7-27c703df9c8c",
    "service": "viza",
    "status": "pending",
    "type": "check_out",
    "reason": "Report arrived from PMS",
    "context": {
      "occurredAt": "1986-10-07 13:01:29",
      "guests": [
        {
          "id": "c5a366f4-a667-3e83-b691-9074430c20dd",
          "departure": "1984-02-17 07:30:40"
        }
      ]
    },
    "response": null,
    "createdAt": "2022-11-10T11:10:2700:00",
    "updatedAt": "2022-11-10T11:10:2700:00"
  }
}
Last updated on
Check In