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
  • If you use Gladstone
  • If you use Legend
  • How do I know if my open data feed has been activated?
  • If you use a different booking system
  1. platform products
  2. Live Timetables

Pre-Requisites: Open Data Feeds

PreviousLive TimetablesNextThe Onboarding Process

Last updated 1 year ago

In order to use the Live Timetables, you will need to have activated an OpenActive-compliant open data feed from your booking system or LMS. We use this OpenActive data feed in order to populate the Live Timetables.

The OpenActive open data feed is near real-time feed, so when the information is updated within your booking system (e.g. a class gets cancelled, moved, or a space is booked by a customer) it will automatically reflect in the data feed and therefore the Live Timetable.

These feeds can take several weeks to be turned on, so we recommend following the steps below asap:

If you use Gladstone

You will need contact your Gladstone account manager or support desk to request the activation of the Gladstone add-on called "OpenActive Web Services" (OWS). Depending on your arrangement with Gladstone, this may incur a fee upfront and / or on-going - your Gladstone point of contact will be able to clarify this for you.

If you use Legend

You will need to ask your Legend account manager to "activate our open data feed". This is sometimes called the "ODI feed" within Legend. This should be free for you to access.

How do I know if my open data feed has been activated?

Once activated, your booking system should provide you with a url for your "data set page" - which is a landing page where your open data feed can be accessed from.

Here is an example from Gladstone () and from Legend ().

In addition, if you are a Gladstone customer, they should provide you with a username and password for the OpenActive Data Manager.

If you use a different booking system

Please get in touch with us at support@imin.co and we'll provide specific guidance depending on your setup.

https://data.everyoneactive.com/OpenActive/
https://halo-openactive.legendonlineservices.co.uk/OpenActive