Online Check-in

Just like with an airline, except for tours and activities

To use this capability add octo/checkin to your Octo-Capabilities header.
Some products require online checkin after booking confirmation and before the guest is allowed to use their tickets. This is typically the case when:
The product has waivers that must be signed by each guest.
The product has required questions that need answering (such as dietary requirements).
The product is a multi-part package where each part needs a travel date and time chosen.
If the checkin process is skipped the guest will still be able to complete the check-in process when they arrive, it just may delay their experience.
This capability also provides a way to find an existing booking using either the booking reference number or customer email or mobile.
post
https://api.ventrata.com/octo
/checkin/lookup
Lookup
Your first step is to pick with of the 3 pieces of information you'd like to use to lookup the customer's booking:
Email We'll then send a verification code to the customer's email which you'll need to repeat in the request to verify the guest's identity. 
Mobile We'll then send a verification code to the customer's email which you'll need to repeat in the request to verify the guest's identity. 
Reference If the booking exists we will then ask for a last name to verify the the guest's identity.
Some example requests for each type are shown below:
Email
Mobile
Reference
Reference with no last name
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "email": "[email protected]"
}
HTTP/1.1 200 OK
Content-Type: application/json
​
{
  "message": "A verification email has been sent to [email protected]",
  "verified": false,
  "bookings": []
}
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "mobile": "+447840739430"
}
HTTP/1.1 200 OK
Content-Type: application/json
​
{
  "message": "A verification SMS has been sent to +44 (0) 7840 739430",
  "verified": false,
  "bookings": []
}
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "reference": "X1P2FY"
}
HTTP/1.1 200 OK
Content-Type: application/json
​
{
  "message": "Customer last name required for verification",
  "verified": false,
  "bookings": []
}
The same as reference, except if this time the booking no last name to verify with, the request is immediately verified:
HTTP/1.1 200 OK
Content-Type: application/json
​
{
  "message": null,
  "verified": true,
  "bookings": [
    {
      // ... rest of the booking object
      "checkedIn": false,
      "checkinAvailable": true,
      "checkinUrl": "https://website.com/en/checkin?order_token=6d2d9d36-8001-41c6-b716-fccfb5117cf9&booking=1ec5dae4-230e-495d-80b7-0fd5def983f5"
    }
  ]
}
If no booking was found using the email, mobile or reference provided we will instead return a 400 Bad Request response with an appropriate error message.
At this point, provided the request is not already verified, we will have sent a verification code to via Email or SMS, or request a last name. You should prompt the guest to enter this and then repeat the request with the verification parameter provided.
Email
Mobile
Reference
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "email": "[email protected]",
  "verification": "815924"
}
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "mobile": "+447840739430",
  "verification": "057823"
}
POST /checkin/lookup HTTP/1.1
Content-Type: application/json
Host: api.ventrata.com/octo
​
{
  "reference": "X1P2FY",
  "verification": "last_name"
}
Provided that the verification code is correct, we'll then respond with a verified response that looks like this:
{
  "message": null,
  "verified": true,
  "bookings": [
    {
      // ... rest of the booking object
      "checkedIn": false,
      "checkinAvailable": true,
      "checkinUrl": "https://website.com/en/checkin?order_token=6d2d9d36-8001-41c6-b716-fccfb5117cf9&booking=1ec5dae4-230e-495d-80b7-0fd5def983f5"
    }
  ]
}
We've omitted many of the booking object fields to simply the documentation, but all the fields documented here will be included.
Also note it's possible that the information provided might have returned more than one booking. We'll return them in order of date confirmed (most recent at the top).
get
https://api.ventrata.com/octo
/bookings/:uuid
Checkin Status
With this capability enabled we'll add checkedIn checkinAvailable and checkinUrl to each booking. A sample of just these changes are:
{
  // ... rest of the booking object
  "checkedIn": false,
  "checkinAvailable": true,
  "checkinUrl": "https://website.com/en/checkin?order_token=6d2d9d36-8001-41c6-b716-fccfb5117cf9&booking=1ec5dae4-230e-495d-80b7-0fd5def983f5"
}
Field
Definition
checkedIn
Whether the booking is checked in already
checkinAvailable
If true then check-in is available for this booking and you can offer it to the guest. We strongly encourage you to do this as it will speed up entry for the guest before they arrive.
checkinUrl
This is the URL to send the guest to complete their checkin. This value will be set if checkinAvailable is true otherwise it will be null

Last modified 2yr ago

Field	Definition
`checkedIn`	Whether the booking is checked in already
`checkinAvailable`	If true then check-in is available for this booking and you can offer it to the guest. We strongly encourage you to do this as it will speed up entry for the guest before they arrive.
`checkinUrl`	This is the URL to send the guest to complete their checkin. This value will be set if checkinAvailable is true otherwise it will be `null`