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
  • Schedules
  • Daily
  • Weekly
  • Monthly
  • PartialSchedules
  1. Info for Data Publishers
  2. Your RPDE Feed & the imin Platform [BETA]

Providing Schedule Information [BETA]

Schedules

At present, our Platform only supports:

  • repeatFrequency - daily, weekly and monthly.

  • byDay - schema days (not iCal).

  • byMonthDay - numbers.

Our platform does not currently support iCal-type rules like 1TH (or -2WE, etc.).

Daily

The following is an example of a session that takes place every other day:

{
  "@context": [
    "https://openactive.io/"
  ],
  "@type": "Schedule",
  "repeatFrequency": "P2D",
  "startDate": "2018-10-19",
  "endDate": "2018-11-04",
  "startTime": "08:30",
  "endTime": "09:30",
  "duration": "PT1H",
  "scheduleTimezone": "Europe/London",
  "scheduledEventType": "ScheduledSession",
  "idTemplate": "https://example.com/api/scheduled-sessions/{startDate}",
  "urlTemplate": "https://example.com/scheduled-sessions/{startDate}"
}

Daily must be used with neither byDay nor byMonthDay.

Weekly

The following session will take place every week on Tuesday and Sunday:

{
  "@context": [
    "https://openactive.io/"
  ],
  "@type": "Schedule",
  "repeatFrequency": "P1W",
  "startDate": "2018-10-19",
  "endDate": "2018-11-04",
  "startTime": "08:30",
  "endTime": "09:30",
  "byDay": [
    "https://schema.org/Tuesday",
    "https://schema.org/Sunday"
  ],
  "duration": "PT1H",
  "scheduleTimezone": "Europe/London",
  "scheduledEventType": "ScheduledSession",
  "idTemplate": "https://example.com/api/scheduled-sessions/{startDate}",
  "urlTemplate": "https://example.com/scheduled-sessions/{startDate}"
}

Weekly must be used with byDay but not byMonthDay.

Monthly

This session happens every month on the 5th and on the 15th:

{
  "@context": [
    "https://openactive.io/"
  ],
  "@type": "Schedule",
  "repeatFrequency": "P1M",
  "startDate": "2018-10-05",
  "endDate": "2018-12-15",
  "startTime": "08:30",
  "endTime": "09:30",
  "duration": "PT1H",
  "byMonthDay": [
    5,
    15
  ],
  "scheduleTimezone": "Europe/London",
  "scheduledEventType": "ScheduledSession",
  "idTemplate": "https://example.com/api/scheduled-sessions/{startDate}",
  "urlTemplate": "https://example.com/scheduled-sessions/{startDate}"
}

Monthly must be used with byMonthDay and not byDay.

PartialSchedules

PreviousProviding Places Data [BETA]

Last updated 4 years ago

If you are including PartialSchedules in your data, we highly recommend that you also include the oa:schedulingNote property, found in the , to alert the end user to the fact that the session may or may not be taking place.

OpenActive Specification