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
  • Terminology
  • Request
  1. incorporating book and pay
  2. imin Branded Checkout
  3. Authenticated Checkout

Group Booking [BETA]

Do a Group Booking with Authenticated Checkout

PreviousTesting [BETA]NextStandalone Checkout

Last updated 2 years ago

Multiple attendees can be booked onto a single to attend the same activity. Such a Group Booking can be done using very similarly to booking for a single attendee.

Terminology

  • Customer: The person who is paying for the booking. This is the person who is contacted about changes to the booking (e.g. cancellation) and receives confirmation email

  • Attendee: A person who will be attending the booked activity. NOTE: Often, the customer will also be an attendee and so their ID will be included twice in the Authenticated Checkout request — once as Customer and once as Attendee.

Request

POST /api/checkout-sessions

{
  "@context": ["https://openactive.io/", "https://imin.co/"],
  "type": "imin:CheckoutSession",
  "imin:initialOrder": {
    "type": "OrderQuote",
    "customer": "<< Customer ID >>",
    "broker": {
      "type": "Organization",
      "name": "<< Broker name >>",
      "url": "<< Broker home page URL >>"
    },
    "orderedItem": [
      {
        "type": "OrderItem",
        "orderedItem": {
          "type": "<< Opportunity Type >>",
          "identifier": "<< Opportunity Identifier >>"
        },
        "acceptedOffer": "<< Offer ID >>",
        "attendee": "<< Attendee #1 ID >>"
      },
      {
        "type": "OrderItem",
        "orderedItem": {
          "type": "<< Opportunity Type >>",
          "identifier": "<< Opportunity Identifier >>"
        },
        "acceptedOffer": "<< Offer ID >>",
        "attendee": "<< Attendee #2 ID >>"
      }
    ]
  },
  "imin:navigationLinks": [
    {
      "type": "WebPage",
      "name": "Back to Broker",
      "imin:linkType": "https://imin.co/BackToBrokerLink",
      "url": "<< back to broker URL >>"
    },
    {
      "type": "WebPage",
      "name": "Back to Broker User Profile",
      "imin:linkType": "https://imin.co/BackToBrokerUserProfileLink",
      "url": "<< back to broker user profile URL >>"
    }
  ]
}
  • customer MUST be a Customer Account ID. Customer object is not allowed for Group Booking.

  • There are multiple OrderItems. Please include one OrderItem for each Attendee.

Constraints:

  • Only one activity at a time can be booked. In practice, this means that each OrderItem must have the same values for orderedItem and acceptedOffer.

How this differs from the single-attendee request documented in :

Each OrderItem has a required attendee field. Like customer, this accepts an imin Customer Account ID (info on Customer Account management ). As mentioned above, the ID used in customer may, and often will, also be used as one of the attendees if the person who is booking the activity is also going to attend it.

👪
Order
Authenticated Checkout
here
the Authenticated Checkout docs