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
  4. ByID Search

Slot By-ID

PreviousFacilityUse By-IDNextFacilityUses and IndividualFacilityUses

Last updated 2 years ago

The Slot.ids returned in either an upcoming-slots query parameter search or a FacilityUse ByID search can be used to make a Slot ByID search.

Every FacilityUse will have an event[].id or an event[].event[].id (in the case where there are IndividualFacilityUses) which will be a URL that looks like https://search.imin.co/facilities-api/v2/slots/{Slot.id}. This should be used for Slot ByID searches. Each Slot.id is appended with YYYY-MM-DDTHH:MM:SS, depending on the startDate of the Slot.

The Slot.ids returned will depend on which search route is used:

  1. Slot ByID search following upcoming-slots query parameter search: the Slot.ids will include a YYYY-MM-DD that exactly matches the startDate included in the initial upcoming-slots search.

  2. Slot ByID search following FacilityUse ByID search: the Slot.ids will include YYYY-MM-DDs as far ahead 7 days in the future.

Slot By-ID searches return a slot for one facility on day at a specific time: one facility + one day + one slot.

Slot By-ID Search Example

would return one slot at a specific time on a specific date for a specific FacilityUse:

  • 4 available badminton courts in a sport hall;

  • On 3000-01-05;

  • At 06-30-00.

https://search.imin.co/facilities-api/v2/slots/{Slot.id }3000-01-05T06-30-00