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
  • startDate
  • ids
  1. platform products
  2. Search
  3. imin Facilities API
  4. Query Parameter Search
  5. Mandatory Query Parameters

mode=upcoming-slots

Previousmode=discovery-geoNextOptional Query Parameters

Last updated 4 years ago

The upcoming-slots query parameter search can be used to return slots for multiple facilities on a specific day, i.e. multiple facilities + one day + slots.

startDate

When using upcoming-slots, the startDate[gte]or startDate[lte] parameter must be included. The results returned will contain time-based information pertaining to one specific day (the startDate) and be ordered chronologically.

There are three behaviours to bear in mind when using startDate:

  1. When only startDate[gte] is used, the API will return slots from that time until the end of the day, e.g. startDate[gte]=3000-01-01T09:00:00Z will return slots between 09:00:00-23:59:59 on3000-01-01;

  2. When only startDate[lte] is used, the API will return slots from the start of the day until that time, e.g. startDate[lte]=3000-01-01T13:30:00Z will return slots between 00:00:00-13:29:59 on3000-01-01; and

  3. The startDate[gte] and startDate[lte], when used in combination, can only span one calendar day, i.e. it is not possible to include two different dates when using the Facilities API.

startDate Examples

would return:

  • Thoseled facilities;

  • Within a 100km radius of 51.05602333,-2.423247080;

  • That have the activity Tennis; and

  • All available slots between 16:00:00-23:59:59 on 3000-01-03.

would return:

  • All of the above; except for

  • All available slots between 16:00:00-20:59:59 on 3000-01-03.

The example queries above will not generate any results. This is because the startDate provided is outside of the Platform's 2-week API lookahead window.

ids

An upcoming-slots search will return two ids for each FacilityUse:

The two ids offer the following options:

Anupcoming-slotssearch will always return an event array, which will contain one or more Slots relevant to the startDate included in the API call.

The FacilityUse id: this root URL, which looks like , will form the basis of the .

The Slot id: this is a URL that can be found in the FacilityUse at theevent array. Every Slot id, which looks like , forms the basis of the .

i) The FacilityUse id = one facility + multiple days + slots ().

ii)Slot By-ID = one facility + one day + one slot ()

https://search.imin.co/facilities-api/v2/facility-uses?geo[radial]=51.05602333,-2.423247080,100&mode=upcoming-slots&limit=50&page=1&providerId=led&activityPrefLabel=Tennis&startDate[gte]=3000-01-03T16:00:00Z
https://search.imin.co/facilities-api/v2/facility-uses?geo[radial]=51.05602333,-2.423247080,100&mode=upcoming-slots&limit=50&page=1&providerId=led&activityPrefLabel=Tennis&startDate[gte]=3000-01-03T16:00:00Z&startDate[lte]=3000-01-03T21:00:00Z
https://search.imin.co/facilities-api/v2/facility-uses/{identifier}
FacilityUse ByID search
https://search.imin.co/facilities-api/v2/slots/{event[].id }
Slot ByID search
FacilityUse ByID Search
Slot ByID Search