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. HINTS & TIPS
  2. Get the Best Out of Search

Your Search Results and HighFrequencySessions

PreviousSearching by ActivityNextCustomer Specific Images

Last updated 2 years ago

For an introduction to HighFrequencySessions, please refer to .

The default behaviour of the Events API is to include iminTag[not]=HighFrequencySession in every call. As a result of this, a general Events API search will return neither swimming nor gym workout sessions. This is due to the sheer volume of these types of sessions in our Platform.

HighFrequencySessions include items provided by leisure operators that have either Swimming or Gym Workout as the activityPrefLabel.

If you are offering users the ability to search for Swimming and/or gym workout, and you are relying on the default behaviour of the Events API, i.e. your API calls include iminTag[not]=HighFrequencySession, then the number of sessions returned will be vastly reduced.

For example, the following API call will return a very smaller number of items that have Swimming as the activityPrefLabel:

https://search.imin.co/events-api/v2/event-series?mode=upcoming-sessions&geo[radial]=51.2422774,-0.7294026,50&limit=50&activityId=https%3A%2F%2Fopenactive.io%2Factivity-list%232750229d-b725-4171-9276-376be913957c

This is because iminTag[not]=HighFrequencySession is filtering out the large of swimming sessions contained in the Platform that would otherwise match the given parameters.

Please note that the absence of iminTag[not]=HighFrequencySession in the above API call does not mean it is not there. It just serves to illustrate the default behaviour of the Events API, i.e. filter the results to exclude swimming and gym workout sessions as standard. One way to check this is to look at view.id in the results of the above API call, which will make reference to iminTag%5Bnot%5D%3DHighFrequencySession even though it is not included it in the initial API call.

If you want to return all available swimming sessions, you will need to include iminTag=HighFrequencySession, i.e. exclude the [not] from the API call.

For example, the following API call will return tens of thousands of items that have Swimming as the activityPrefLabel:

https://search.imin.co/events-api/v2/event-series?mode=upcoming-sessions&geo[radial]=51.2422774,-0.7294026,50&limit=50&iminTag=HighFrequencySession&activityId=https%3A%2F%2Fopenactive.io%2Factivity-list%232750229d-b725-4171-9276-376be913957c

If you want to return swimming or gym workout sessions via the Events API, then you must include iminTag=HighFrequencySession along with the relevant activityId.

Conversely, if you include iminTag=HighFrequencySession in an API call along with an activityId that corresponds to something other than swimming or gym workout, e.g. football, then 0 items will be returned.

iminTag=HighFrequencySession can only be used exclusively when searching for swimming and/or gym workout.

HighFrequencySession