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
  • Accessing the Attribution Catalog Endpoint
  • Using the Attribution Catalog Endpoint with Firehose
  • Displaying attribution to end users
  • Full Example for Fusion Lifestyle
  1. platform products
  2. Firehose

Attribution Catalog Endpoint

PreviousBookable Sellers FeedNextLive Timetables

Last updated 2 years ago

It is a licensing requirement (see 3.7.2 of our ) that any frontend that displays open data form the imin Platform must include the relevant open data attribution alongside it.

The Attribution Catalog Endpoint returns metadata of all OpenActive Datasets available through the imin Platform.

Accessing the Attribution Catalog Endpoint

In keeping with the design philosophy of the Firehose API, the endpoints includes metadata for all datasets available through the imin Platform:

https://firehose.imin.co/firehose/datasets

As with other imin endpoints, you must provide a valid API key as the X-API-KEY request header.

Using the Attribution Catalog Endpoint with Firehose

The items within the Attribution Catalog Endpoint will include at least the following properties:

{
  "@context": [
    "https://schema.org/",
    "https://openactive.io/"
  ],
  "@type": "Dataset",
  "@id": "https://data.everyoneactive.com/OpenActive/",
  "identifier": "everyone-active",
  "name": "Everyone Active Sessions and Facilities",
  "publisher": {
    "@type": "Organization",
    "name": "Everyone Active",
    "legalName": "Sports and Leisure Management LTD",
    ...
  },
  "license": "https://creativecommons.org/licenses/by/4.0/",
  ...
}

The data items within the Firehose feeds include the following properties:

"data": {
  ...
  "imin:dataSource": {
    "@type": "Dataset",
    "identifier": "everyone-active"
  }
  ...
}

The value of the data.imin:dataSource.identifier in the Firehose feeds can be matched against the value of identifier in the Attribution Catalog Endpoint, and hence can be used to dereference the complete data for the Dataset.

Displaying attribution to end users

The attribution should be included somewhere on the page where the data appears (i.e. the session or facility page).

The following HTML is recommended for attribution on any opportunity page, based on the data in the Dataset retrieved above:

Source: <a href="{{Dataset.url}}" property="odrs:attributionURL">
    <span property="odrs:attributionText">{{Dataset.publisher.name}}</span>
</a>

Full Example for Fusion Lifestyle

For a Firehose feed opportunity that includes a Dataset.identifier as follows:

"imin:dataSource": {
  "@type": "Dataset",
  "identifier": "fusion-lifestyle"
}

The following matching data should be retrieved from the Attribution Catalog Endpoint:

{
  "@type": "Dataset",
  "identifier": "fusion-lifestyle",
  "url": "https://opendata.fusion-lifestyle.com/OpenActive/",
  "publisher": {
    "@type": "Organization",
    "name": "Fusion Lifestyle",
    ...
  },
  ...
}

And rendered into the following HTML for display to the user:

Source: <a href="https://opendata.fusion-lifestyle.com/OpenActive/" property="odrs:attributionURL">
    <span property="odrs:attributionText">Fusion Lifestyle</span>
</a>

Which is displayed as follows:

It is a licensing requirement (see 3.7.2 of our ) that any frontend that displays open data from the imin Platform must include the relevant open data attribution alongside it.

For example, for data from Everyone Active, the attribution should be hyperlinked as follows somewhere on a page displaying that data, as stipulated at the bottom of its Dataset Site at :

Source:

Source:

Service Terms of Use
Service Terms of Use
https://data.everyoneactive.com/OpenActive/
Everyone Active
Fusion Lifestyle