Pricing
The pricing
configuration parameter is used to define the prices and ticket types for your event. It determines which price ticket buyers see when they hover objects on the chart.
Configuration
Type: object
{
pricing: {
allFeesIncluded?: boolean
prices: object[]
priceFormatter?: price => string
showSectionPricingOverlay?: boolean
}
}
allFeesIncluded
: Set to show prices including or excluding fees. If not set, nothing is shown. Can be used in conjunction with fees per price entry to show exact fees.prices
: the prices and ticket types, per category, channel or objectpriceFormatter
: a function that formats the price for display, typically by adding a currency symbolshowSectionPricingOverlay
: whether to show the pricing on top of sections
Legacy configuration
As of June 2025, we have introduced a new object format that groups the old top-level properties. While we still support the old configuration, this will be deprecated at a later time.
This change was made to allow future configuration expansion and introduce stricter validation. For instance, it is no longer possible to define prices as string.
Migration to the object-based format
If your existing pricing configuration adheres to our schemas (e.g. it doesn't use strings for prices or set custom properties), you should only need to move your pricing array into the new pricing.prices
property. The same goes for priceFormatter
and showSectionPricingOverlay
, which should be moved from the top level configuration and inside the pricing object.
Example
// From:
config = {
// ...other config properties,
showSectionPricingOverlay: true,
priceFormatter: (price) => price + '€',
pricing: [
{ category: 'Ground Floor', price: 35 },
{ category: ''}
]
}
// To:
config = {
// ...other config properties,
pricing: {
showSectionPricingOverlay: true,
priceFormatter: (price) => price + '€',
prices: [
{ category: 'Ground Floor', price: 35 },
{ category: ''}
]
}
}