Introduction

OneBasket is a direct-to-consumer commerce platform for sports organisations. It collects products and services from separate provider systems, such as ticketing, retail, and food and beverage, and exposes them through one API.

A customer adds products from any provider to one basket and pays with one payment. OneBasket then creates the order with each provider and tracks fulfilment. The customer stays inside the organisation's own website or app for the whole purchase.

What you can build

• Product listing and product detail screens that combine products from several providers.
• Cross-sells between products from different providers.
• A single basket and a single checkout for all products.
• Post-purchase screens, such as ticket wallets, ticket forwarding, and order collection at a kiosk.

The Storefront API

The Storefront API is the set of REST endpoints that customer-facing websites and apps call. It is documented in the API reference. It is split into these APIs:

Where to start

1. Read Core concepts to learn the terms used across the APIs.
2. Follow the Quickstart to make your first requests.
3. Read Authentication and Asynchronous operations. Every integration needs both.

Getting access

You need an API key for a store before you can call the Storefront API. Your Stadion technical contact issues API keys and tells you the base URL for your store.