The imin Platform
2.0.0
2.0.0
  • Introduction to the imin Platform
  • Using the Platform
    • imin's Platform Products
    • Authentication
    • Our Platform Data
      • Understanding Responses
      • Namespaces and Extensions
      • Defensive Data Consumption
      • Mocking the Interface
  • platform products
    • Search
      • imin Events API
        • Events API Reference
        • Virtual & Physical Sessions
        • Concepts
          • EventSeries
          • ScheduledSessions and eventSchedules
          • Activities and Collections
            • Activities
            • Activity Concept Collections
          • Accessibility Support
          • Prices
        • Filters
          • Modes
          • Age Ranges
          • Dates and Times
          • Activities and Concept Collections
          • High Frequency Sessions
      • imin Facilities API
        • Query Parameter Search
          • Mandatory Query Parameters
            • mode=discovery-geo
            • mode=upcoming-slots
          • Optional Query Parameters
        • ByID Search
          • FacilityUse By-ID
          • Slot By-ID
        • FacilityUses and IndividualFacilityUses
        • Slots
        • Facilities Slot Booking
      • imin Places API [BETA]
        • Example Request & Response
    • Firehose
      • Introduction to the Firehose
      • Accessing the Firehose
      • Firehose Usage Policy & Restrictions
      • Firehose and Search
      • Bookable Firehose Feeds
      • Bookable Sellers Feed
      • Attribution Catalog Endpoint
    • Live Timetables
      • Pre-Requisites: Open Data Feeds
      • The Onboarding Process
        • 1. Ensuring your Data Offers the Best User Experience
        • 2. Setting up and Embedding your First Timetable
        • 3. Setting up the Rest of your Timetables
        • 4. Activating Booking via Guest Checkout
      • Features Available Upon Request
      • Styling the Live Timetables
      • FAQs
    • Data Dashboard
  • incorporating book and pay
    • imin Branded Checkout
      • Introduction
      • Setup
        • Information We Require From You
        • Actions You Need to Complete
      • Authenticated Checkout
        • Testing [BETA]
        • 👪Group Booking [BETA]
      • Standalone Checkout
      • Firehose and Checkout [BETA]
        • Loading the Checkout via Firehose
    • imin Booking Platform
      • Customer Account Management
        • Create Customer Account
        • Update Customer Account
        • Get Customer Account
        • Delete Customer Account
        • Example Scenario
        • Payment Card Management
        • Linked Accounts
        • Entitlement
          • Evidence Requests
          • Entitlement Pricing in Search
          • Entitlement Pricing in Checkout
        • Access Pass
        • Webhooks
      • Orders
        • Order History
        • Order (by ID)
        • Cancellations & Refunds
      • Upcoming OrderItems
      • Receipt (by ID)
  • imin and booking systems
    • Seller Onboarding
      • API
  • HINTS & TIPS
    • Get the Best Out of Search
      • Displaying Schedule Information
      • URLs and Offering a Call to Action
      • Searching by Activity
      • Your Search Results and HighFrequencySessions
      • Customer Specific Images
  • Info for Data Publishers
    • Your RPDE Feed & the imin Platform [BETA]
      • Providing Places Data [BETA]
      • Providing Schedule Information [BETA]
Powered by GitBook
On this page
  1. platform products
  2. Search
  3. imin Facilities API

Slots

PreviousFacilityUses and IndividualFacilityUsesNextFacilities Slot Booking

Last updated 2 years ago

A Slot is a specific time (THH:MM:SSZ) on a specific date (YYYY-MM-DD) upon which a FacilityUse is available.

Once a or search has been made, more information about a Slot will be presented by the API. This will include information that was available at Discovery search, such as startDate and remainingUses, but also more specific information such as Slot-specific Offers, sportsActivityLocations, etc. More information about Slot-specific information can be found in the .

Slots can be found in one of two places in a FacilityUse depending on underlying data structure from the provider:

  1. FacilityUse.event[] (FacilityUses without IndividualFacilityUses)

  2. FacilityUse.event[].event[] (FacilityUses with IndividualFacilityUses)

For more information about FacilityUses and IndividualFacilityUses, please see FacilityUses and IndividualFacilityUses

maximumUses & remainingUses in relation to sportsActivityLocations

A Slot relating to a specific FacilityUse might have one or more sportsActivityLocations available.

This will only be the case if the FacilityUse does not have any IndividualFacilityUses, which fulfil the same role.

For example, there might be 6 badminton courts in a sports hall, all of which are included within the same FacilityUse. In this instance:

  • The total number of courts (6) is reflected in maximumUses;

  • The number of courts still available is reflected in remainingUses; and

  • The information about the courts still available is included within the beta:sportsActivityLocation array.

maximumUses refers to the total number of courts available for a specific FacilityUse and, as such, always remains the same. It does not account for courts that have been booked and does not serve to indicate the number of people who can attend.

Example

Looking at the JSON below you can see that there are 6 courts available (maximumUses) and that 2 of them have been booked, leaving 4 remainingUses. The beta:sportsActivityLocation[].name shows the courts that are still available.

"maximumUses": 6,
"remainingUses": 4,
"beta:sportsActivityLocation": [
    {
        "name": "Main Hall Court 1",
        "type": "SportsActivityLocation",
        "identifier": "188ZMHAL01"
    },
    {
        "name": "Main Hall Court 3",
        "type": "SportsActivityLocation",
        "identifier": "188ZMHAL03"
    },
    {
        "name": "Main Hall Court 4",
        "type": "SportsActivityLocation",
        "identifier": "188ZMHAL04"
    },
    {
        "name": "Main Hall Court 6",
        "type": "SportsActivityLocation",
        "identifier": "188ZMHAL06"
    }
],
FacilityUse By-ID
Slot By-ID
Modelling Specification