{
  "opencollection": "1.0.0",
  "info": {
    "name": "Open Connectivity for Tours, Activities, and Attractions OCTO API Specification Availability API",
    "version": "1.0"
  },
  "items": [
    {
      "info": {
        "name": "Availability",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Open Connectivity for Tours, Activities, and Attractions Availability Calendar",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.example.com/octo/availability/calendar",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "This endpoint is highly optimised and will return a single object per day. It's designed to be queried for large date ranges and the result is used to populate an availability calendar.\n\nWhen the end user selects an open date you can call on `/availability` endpoint to get the `availabilityId` to create the booking."
        },
        {
          "info": {
            "name": "Open Connectivity for Tours, Activities, and Attractions Availability Check",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.example.com/octo/availability",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "This endpoint is slightly slower as it will return an object for each individual departure time (or day). You have to perform this step to retrieve an `availabilityId` in order to confirm a sale, so if you just want to use this endpoint and skip the calendar endpoint then that's perfectly ok.\n\nYou must pass in one of the following combinations of parameters for this endpoint:\n- `localDate`\n- `localeDateStart` and `localDateEnd`\n- `availabilityIds`"
        }
      ]
    }
  ],
  "bundled": true
}