aid: fever
name: Fever
description: >-
Fever is a global live-entertainment discovery and ticketing platform that
helps millions of people find events, activities and experiences in their
city, and gives venues and partners the tools to sell and analyze tickets.
For developers Fever exposes two public surfaces: an official Model Context
Protocol (MCP) server over its real-time global event catalog (tools
search_cities and search_events, OAuth 2.0 with PKCE), and a partner-facing
Reporting API delivering in-depth event sales data (orders, tickets,
financials, plan and session details) for CRM, BI, data-warehouse and ERP
integration. Fever is backed by Accel and General Catalyst.
url: https://raw.githubusercontent.com/api-evangelist/fever/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service Β· you call their endpoint
confidence: medium
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: self-serve
trial: false
try_now: false
public: false
label: Self-serve signup
confidence: medium
source:
- authentication
generated: '2026-07-22'
method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://feverup.com/_astro/og-image-fever.PfP_3GVw.jpg
tags:
- Company
- Consumer
- Live Entertainment
- Event
- Ticketing
- Experience
- Reporting
- MCP
tags_raw:
- Company
- Consumer
- Live Entertainment
- Events
- Ticketing
- Experiences
- Reporting
- MCP
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
apis:
- aid: fever:fever-authentication-api
name: Fever Authentication API
description: >-
This endpoint is used to authenticate a user. It requires a username and password to be passed in
the request body. If
the user is authenticated successfully, a token is returned in the response body. This token is used
to authenticate the
user in subsequent requests.
β οΈ The token expiration time is **30 minutes**. After that time, the user will need to authenticate
again to get a new token.
humanURL: https://developer.feverup.com/en/
baseURL: https://data-reporting-api.prod.feverup.com/v1
tags:
- Authentication
properties:
- type: OpenAPI
url: openapi/fever-authentication-api-openapi.yml
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: Authentication
url: authentication/fever-authentication.yml
- aid: fever:fever-feverzone-api
name: Fever FeverZone API
description: >-
These endpoints provide an interface to extract the data available in FeverZone reports. The delay
of the data
is less than 15 minutes from reality. The route `/feverzone/sales-by-reseller` allows the user to
get a sales summary
by reseller and can be aggregated by venues/ticket types.
## Model documentation
#### Sales
This endpoint returns a summary of the sales, aligned with FeverZone Sales Summary report. It allows
to filter by
`plan_ids`, `purchase_date` and `event_date`, and also specify the `currency` of the report.
π /feverzone/sales-summary response entity model
| Column Name | Description |
Example value |
|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| `currency` | ISO3 currency of the order monetary field. |
EUR |
| `orders` | Metric representing the number of unique transactions (count) made, where
each order may include multiple tickets and add-ons. |
100 |
| `tickets_sold` | Metric representing the number (sum) of entry tickets sold, excluding any
complimentary tickets issued (invitations) and add-ons. This value shows the total number of entry
tickets, representing the primary sales volume. |
200 |
| `addons_sold` | Metric representing the number (sum) of add-ons sold, excluding complimentary
invitations. Indicates the total number of add-ons purchased. |
50 |
| `ticket_invitations` | Metric representing the number (sum) of complimentary tickets issued at
no charge for the user. Issuing invitations may have fees. |
10 |
| `addons_invitations` | Metric representing the number (sum) of complimentary add-ons issued at
no charge. Issuing add-ons may have fees. |
5 |
| `ticket_gross_revenue` | Metric representing the revenue generated exclusively from the sale of
entry tickets. It's the sum of `tickets_sold` multiplied by their ticket price. It shows the financial
contribution of ticket sales to the total revenue. |
1200.00 |
| `addon_gross_revenue` | Metric representing the revenue generated from the sale of additional items
or services, such as merchandise or premium experiences (a.k.a. add-ons). It's the sum of `addons_sold`
multiplied by their add-on price. It indicates the contribution of supplementary products or services
to total revenue. | 356.34 |
| `total_gross_revenue` | Metric representing the total amount of revenue generated from ticket sales
and add-ons, including surcharge, and before any discounts are applied. It equals to `ticket_gross_revenue`
+ `addon_gross_revenue` + `surcharge`. Indicates the overall financial performance, showing the total
revenue collected from sales and additional charges before considering any discounts. | 1556.34 |
| `ticket_surcharge` | Metric representing the surcharges applied specifically to entry ticket
sales. It's the sum of `tickets_sold` multiplied by their surcharge per ticket. It provides details
on the extra fees associated with entry ticket purchases. |
56.34 |
| `addon_surcharge` | Metric representing the surcharges applied specifically to add-ons. It's
the sum of `addons_sold` multiplied by their surcharge per add-on. It shows the extra fees collected
from add-on purchases. |
0.00 |
| `surcharge` | Metric representing the sum of additional booking fees applied to the order
at checkout. It's the sum of `ticket_surcharge` and `addon_surcharge`. It represents extra charges
collected. |
56.34 |
| `discount` | Metric representing the total value of all discounts applied through promo
codes or special offers. It's the sum of all discounts applied, and it's represented with a negative
value. It indicates the amount of revenue that has been reduced due to promotional efforts. |
-100.00 |
| `user_payment` | Metric representing the total revenue collected after discounts. It is
computed as the `total_gross_revenue` + `discounts`. It reflects actual revenue paid by customers. |
1456.34 |
π /feverzone/sales-by-ticket-type response entity model
| Column Name | Description |
Example value |
|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| `currency` | ISO3 currency of the order monetary field. |
EUR |
| `ticket_type` | Type of ticket sold. |
Adult |
| `tickets_sold` | Metric representing the number (sum) of entry tickets sold, excluding any
complimentary tickets issued (invitations) and add-ons. This value shows the total number of entry
tickets, representing the primary sales volume. |
200 |
| `addons_sold` | Metric representing the number (sum) of add-ons sold, excluding complimentary
invitations. Indicates the total number of add-ons purchased. |
50 |
| `ticket_invitations` | Metric representing the number (sum) of complimentary tickets issued at
no charge for the user. Issuing invitations may have fees. |
10 |
| `addons_invitations` | Metric representing the number (sum) of complimentary add-ons issued at
no charge. Issuing add-ons may have fees. |
5 |
| `ticket_gross_revenue` | Metric representing the revenue generated exclusively from the sale of
entry tickets. It's the sum of `tickets_sold` multiplied by their ticket price. It shows the financial
contribution of ticket sales to the total revenue. |
1200.00 |
| `addon_gross_revenue` | Metric representing the revenue generated from the sale of additional items
or services, such as merchandise or premium experiences (a.k.a. add-ons). It's the sum of `addons_sold`
multiplied by their add-on price. It indicates the contribution of supplementary products or services
to total revenue. | 356.34 |
| `total_gross_revenue` | Metric representing the total amount of revenue generated from ticket sales
and add-ons, including surcharge, and before any discounts are applied. It equals to `ticket_gross_revenue`
+ `addon_gross_revenue` + `surcharge`. Indicates the overall financial performance, showing the total
revenue collected from sales and additional charges before considering any discounts. | 1556.34 |
| `ticket_surcharge` | Metric representing the surcharges applied specifically to entry ticket
sales. It's the sum of `tickets_sold` multiplied by their surcharge per ticket. It provides details
on the extra fees associated with entry ticket purchases. |
56.34 |
| `addon_surcharge` | Metric representing the surcharges applied specifically to add-ons. It's
the sum of `addons_sold` multiplied by their surcharge per add-on. It shows the extra fees collected
from add-on purchases. |
0.00 |
| `surcharge` | Metric representing the sum of additional booking fees applied to the order
at checkout. It's the sum of `ticket_surcharge` and `addon_surcharge`. It represents extra charges
collected. |
56.34 |
| `discount` | Metric representing the total value of all discounts applied through promo
codes or special offers. It's the sum of all discounts applied, and it's represented with a negative
value. It indicates the amount of revenue that has been reduced due to promotional efforts. |
-100.00 |
| `user_payment` | Metric representing the total revenue collected after discounts. It is
computed as the `total_gross_revenue` + `discounts`. It reflects actual revenue paid by customers. |
1456.34 |
π /feverzone/sales-by-reseller response entity model
| Column Name | Description |
Example value |
|--------------------------------|----------------------------------------------------------------|--------------------------------------|
| `reseller.id` | ID of the reseller |
607f50e3-666f-4b2e-9620-38aabf6d9m10 |
| `reseller.name` | Name of the reseller |
Reseller name |
| `reseller.email` | Email of the reseller |
test@reseller.com |
| `reseller.type` | Type of reseller |
AGENCY |
| `reseller.contact_language` | Language that the reseller uses for communications |
es_ES |
| `reseller.accepts_comms` | If reseller accepts communications or not |
YES |
| `ticket_type` | Ticket type by reseller |
Agencia \| Tarifa BΓ‘sica |
| `venue_name` | Venue name by reseller |
Palacio Real de Madrid |
| `tickets_sold` | Tickets sold by reseller and aggregated dimensions applicable |
1000 |
| `gross_revenue` | Gross revenue by reseller and aggregated dimensions applicable
| 10000 |
humanURL: https://developer.feverup.com/en/
baseURL: https://data-reporting-api.prod.feverup.com/v1
tags:
- FeverZone
properties:
- type: OpenAPI
url: openapi/fever-feverzone-api-openapi.yml
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: Authentication
url: authentication/fever-authentication.yml
- aid: fever:fever-order-items-api
name: Fever Order Items API
description: >-
These endpoints enable to access order-item data.
## Filtering Options
The endpoint supports filtering by:
| Parameter | Type | Description |
|-----------|------|-------------|
| `order_ids` | array[integer] | List of specific order IDs |
| `plan_ids` | array[integer] | List of specific plan (event) IDs |
| `date_field` | string | Date field to filter on (`CREATED_DATE_UTC`, `UPDATED_DATE_UTC`, or `EVENT_START_DATE_UTC`).
`UPDATED_DATE_UTC` filters on when the order **data** last changed (any field of the flattened record,
including nested/enrichment fields such as plan name), matching the `updated_date_utc` field in the
response β not the order's own update time (`order_updated_date_utc`). |
| `date_from` | string | Start date for the selected date field. Format: `YYYY-MM-DD HH:mm` or `YYYY-MM-DD`
|
| `date_to` | string | End date for the selected date field. Format: `YYYY-MM-DD HH:mm` or `YYYY-MM-DD`
|
## Model documentation
#### Orders with Order Items
The goal of this endpoint is to provide a comprehensive picture about orders with detailed information
about their
associated order items, including buyers, owners, partners, plans, sessions, and more.
π /reports/order-items response entity model
| Column Name | Description |
Example value |
|----------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|
| `id` | Unique order ID. This code groups all tickets bought in the same transaction.
| 12345 |
| `parent_order_id` | If the order comes from a reschedule, the original order ID |
11234 |
| `buyer` | Order buyer information. |
_See `order.buyer` documentation below_ |
| `created_date_utc` | UTC date when the order was created. |
2021-01-01T00:00:00Z |
| `updated_date_utc` | UTC date when the order **data** was last updated β moves whenever
any field of the flattened order record changes (including nested/enrichment fields such as plan name,
UTM or ratings). This is the field the `UPDATED_DATE_UTC` filter matches, so filtering by `UPDATED_DATE_UTC`
and this value are always consistent. | 2021-01-01T00:00:00Z |
| `order_updated_date_utc` | UTC date when the order **itself** was last updated (order-level fields
only). Unlike `updated_date_utc`, it does not move when only nested/enrichment data changes. | 2021-01-01T00:00:00Z
|
| `surcharge` | Surcharge applied to the order. |
0.0 |
| `currency` | ISO3 currency of the order monetary fields. |
USD |
| `purchase_channel` | Purchase channel where the transaction comes from. |
web |
| `channel` | Channel slug through which this order was placed. Use this field to
join with `POST /v1/reports/channels/search` β the `channel` field in both endpoints is the same slug.
`null` when no channel is recorded on the order (e.g. box-office or pre-channel data). | partner-channel
|
| `payment_method` | Payment method used. |
credit_card |
| `purchase_location_source` | Purchase location information. |
_See `order.purchase_location_source` documentation below_ |
| `billing_zip_code` | Billing ZIP Code manually fulfilled by the customer. |
28001 |
| `utm` | UTM information attributed to the order. |
_See `order.utm` documentation below_ |
| `partner` | Partner information. |
_See `order.partner` documentation below_ |
| `business` | Business associated with the order. |
_See `order.business` documentation below_ |
| `plan` | Plan information. |
_See `order.plan` documentation below_ |
| `coupon` | Coupon information. |
_See `order.coupon` documentation below_ |
| `assigned_seats` | List of assigned seats for the order. |
_See `order.assigned_seats` documentation below_ |
| `order_items` | List of order items associated with this order. |
_See `order.order_items` documentation below_ |
| `booking_questions` | List of booking questions and answers for the order. |
_See `order.booking_questions` documentation below_ |
| `order_group_id` | π§ **Under Development.** Groups orders from cluster tickets. All orders
with the same `order_group_id` belong to the same purchase group (e.g., bundled tickets across multiple
venues). | 12345 |
| `is_main_group_order` | π§ **Under Development.** Flag indicating whether this is the main order
in a group. `true` for the primary order, `false` for secondary orders in the same group. |
true |
| `staff_notes` | List of staff notes attached to the order. Opt-in: only returned when
the search request includes `included_fields=staff_notes`; otherwise the field is omitted from the
response. | `["Payment Details: Groupon", "change ticket to new day"]` |
| `booked_slots` | List of booked slots (assets/rooms reserved by the cart). |
_See `order.booked_slots` documentation below_ |
| `payment_details` | Card payment details for the order (transaction id, brand and descriptive
payment method). Empty/null when the order was not paid by card or no card details are recorded. |
_See `order.payment_details` documentation below_ |
order.buyer
| Column Name | Description |
Example value |
|------------------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|
| `id` | Unique ID of the buyer. |
123456 |
| `first_name` | First name of the order buyer. |
John |
| `last_name` | Last name of the order buyer. |
Doe |
| `email` | Email of the order buyer. |
test@example.com |
| `date_of_birthday` | Date of birth of the order buyer. |
1990-01-01 |
| `marketing_preference` | Indicates whether the user accepted receiving marketing communications
from the partner in the checkout screen. | true |
| `language` | Language of the order buyer, extracted from the device locale. The format
is ISO 639-1 (two letters). | en |
| `b2b_end_user` | B2B end-user information. `null` when the buyer is not B2B or no B2B end
user is linked to the order. | _See `order.buyer.b2b_end_user` documentation below_ |
order.buyer.b2b_end_user
| Column Name | Description | Example value |
|--------------|-----------------------------------|-------------------|
| `id` | Unique ID of the B2B end user. | 789012 |
| `email` | Email of the B2B end user. | test@feverup.com |
| `first_name` | First name of the B2B end user. | John |
| `last_name` | Last name of the B2B end user. | Doe |
order.purchase_location_source
| Column Name | Description |
Example value |
|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| `id_geo_name` | Geo name ID from where the purchase was made. This field is inferred so it might
not be accurate. More information at https://www.geonames.org/about.html | 123456 |
| `city_name` | City from where the purchase was made. This field is inferred so it might not be
accurate. | Madrid |
| `country_code` | Country code from where the purchase was made. This field is inferred so it might
not be accurate. | ES |
| `region_code` | Region code from where the purchase was made. This field is inferred so it might
not be accurate. | MD |
| `postal_code` | Best estimate of user location at time of purchase, combining multiple sources
of information. | 28001 |
| `quality` | Quality order. |
1.0 |
order.utm
| Column Name | Description |
Example value |
|------------------------|---------------------------------------------------------------------------------|---------------|
| `utm.source` | Value of the UTM source field where the order comes from based on last
click. | google |
| `utm.medium` | Value of the UTM medium field where the order comes from based on last
click. | cpc |
| `utm.campaign` | Value of the UTM campaign field where the order comes from based on last
click. | campaign_1234 |
| `utm.content` | Value of the UTM content field where the order comes from based on last
click. | 692693771262 |
| `utm.term` | Value of the UTM term field where the order comes from based on last click. |
candlelight |
| `utm.referring_domain` | Value of the referring domain where the order comes from. |
google.com |
order.partner
| Column Name | Description | Example value |
|-------------|---------------------------|---------------|
| `id` | Unique ID of the partner. | 1 |
| `name` | Name of the partner. | Partner Name |
order.business
| Column Name | Description | Example value |
|-------------|---------------------------------------------|--------------------------------------|
| `id` | Unique ID of the business. | 7c1caabf-85cd-42ac-96db-524b15443a7b
|
| `name` | Name of the business. | Sample City Tours |
| `tax_id` | Tax identification number of the business. | B12345678 |
order.plan
| Column Name | Description |
Example value |
|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|
| `id` | Unique ID of the plan. |
11 |
| `name` | Name of the plan, providing a short description of the event the client will attend. |
Plan Name |
| `gallery` | List of gallery resources (images / videos) attached to the plan. Opt-in: only returned
when the search request includes `included_fields=gallery`; otherwise the field is omitted from the
response. | _See `order.plan.gallery` documentation below_ |
| `taxonomies` | List of taxonomies attached to the plan. Opt-in: only returned when the search request
includes `included_fields=taxonomies`; otherwise the field is omitted from the response. | _See
`order.plan.taxonomies` documentation below_ |
order.plan.gallery
| Column Name | Description | Example value |
|-------------|----------------------------------------------------------|-------------------------------------|
| `url` | URL of the gallery resource. | https://www.example.com/image.jpg |
| `type` | Type of the gallery resource. One of `image` or `video`. | image |
order.plan.taxonomies
| Column Name | Description | Example value |
|-------------|--------------------|-----------------|
| `id` | Unique taxonomy ID.| 1234 |
| `name` | Taxonomy name. | Taxonomy name |
order.coupon
| Column Name | Description | Example value |
|-------------|------------------------------------------------------------|---------------|
| `name` | Name of the coupon. | Coupon Name |
| `code` | Code of the coupon. | COUPON_CODE |
| `discount` | Discount amount applied by the coupon. | 0.0 |
| `kind` | Coupon kind label (e.g. `No Coupons`, partner-defined). | No Coupons |
order.assigned_seats
| Column Name | Description | Example value |
|-----------------------------------|-------------------------------|---------------|
| `id` | Seat id. | seat_123 |
| `name` | Seat name. | A1 |
| `seating_provider` | Seating provider. | provider_name |
| `seating_provider_seat_reference` | Seating provider's seat name. | ref_123 |
order.booking_questions
| Column Name | Description | Example value |
|-------------|------------------------------------------------|---------------------------------------------|
| `id` | Booking question ID. | f4dd7822-8461-44d6-af47-acdbfd47bf80 |
| `question` | The booking question text. | How did you find out about this experience?
|
| `answers` | List of answers provided by the user. | ["Instagram", "Facebook"] |
| `index` | The index of the question in the booking flow. | 1 |
order.booked_slots
Cart-level array of booked slots. The same array is denormalized across every order in the same cart.
| Column Name | Description |
Example value |
|-------------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|
| `id` | Unique ID of the booked slot. Matches `order_item.booked_slot_id` for every
order item assigned to this slot. | 9876543 |
| `timeslot_utc` | UTC start of the timeslot the slot is booked for. |
2026-05-08T09:30:00Z |
| `slot_count` | Capacity counter from the cart engine. Useful for debugging only β see `party_size`
for the actual people booked. | 12 |
| `occupancy_count` | Number of independent parties booked at the asset for this cart. |
1 |
| `party_size` | Total people (count of order items) sold for this booked slot. |
4 |
| `is_removed` | Whether the slot was removed by the cart engine. |
false |
| `activity` | Activity that owns the booked asset. |
_See `order.booked_slots.activity` documentation below_ |
| `asset` | Asset (e.g. room) the slot is booked on. |
_See `order.booked_slots.asset` documentation below_ |
order.booked_slots.activity
| Column Name | Description | Example value |
|-------------|----------------|-------------------------|
| `id` | Activity ID. | 481 |
| `name` | Activity name. | Escape Room Northbridge |
order.booked_slots.asset
| Column Name | Description |
Example value |
|----------------------------------------------|------------------------------------------------------------------------------|----------------|
| `id` | Asset ID (e.g. an Escape This room). |
3473 |
| `name` | Asset name. |
NB - Asylum |
| `description` | Asset description. | |
| `availability_strategy` | Capacity strategy used by the asset (`BY_PARTY_COUNT`
or `BY_PEOPLE_COUNT`). | BY_PARTY_COUNT |
| `max_party_size` | Maximum number of people allowed in a single party. |
4 |
| `min_party_size` | Minimum number of people required to book a party. |
1 |
| `max_num_parties` | Maximum number of independent parties the asset can
host. | 1 |
| `partner_id` | Partner that owns the asset. |
190 |
| `asset_type_id` | Asset type ID. |
7 |
| `is_manual_assignment_confirmation_required` | Whether the asset requires manual assignment confirmation. |
false |
order.payment_details
Order-level array of card payment details. Empty/null when the order was not paid by card. The same
array is denormalized across every order item belonging to the same order.
| Column Name | Description | Example
value |
|------------------|---------------------------------------------------------------------------|---------------|
| `id` | Transaction ID issued by the payment processor (Braintree, Stripe, ...). | tx_abc123 |
| `card_brand` | Card brand (`visa`, `mastercard`, `amex`, `discover`, ...). | visa |
| `payment_method` | Descriptive payment method joined from the order's payment configuration. | Card |
order.order_items
| Column Name | Description |
Example value |
|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
| `id` | Unique ID of the order item. |
123456 |
| `ticket_id` | Operational identifier of the ticket grouping order items from
the same session. Provided for compatibility with transactional use cases (e.g., reschedules and transfers);
it is not intended as a core reporting metric. |
334455 |
| `booked_slot_id` | ID of the booked slot the order item was assigned to within
its cart, when the activity behind the session uniquely resolves to a single booked slot (e.g. Escape
This rooms). Matches `order.booked_slots[].id`. NULL when the activity exposes more than one asset
and the cart engine spread parties across them; consumers can fall back to substring matching against
`booked_slots[].asset.name`. | 9876543 |
| `cancellation_date_utc` | Last UTC date when any part of the ticket was cancelled. |
2021-01-01T00:00:00Z |
| `cancellation_type` | Type of cancellation. REFUND: means that the ticket has been
cancelled due to a refund. RESCHEDULE: means that the ticket has been cancelled due to a reschedule. |
REFUND |
| `created_date_utc` | UTC date of the ticket creation. |
2021-01-01T00:00:00Z |
| `discount` | Discount applied to the ticket. |
10.0 |
| `is_invite` | Indicates whether the ticket is an invitation from the partner. |
false |
| `modified_date_utc` | UTC date of the last modification of the ticket. |
2021-01-01T00:00:00Z |
| `purchase_date_utc` | UTC date of the ticket purchase. |
2021-01-01T00:00:00Z |
| `event_start_date_utc` | UTC start date of the event associated with this order item. |
2021-01-01T00:00:00Z |
| `validated_date_utc` | UTC date when the order item was validated. This validation
can be independent of the plan code (bar code), since some order items don't have a plan code but
can be validated. |
2021-01-01T00:00:00Z |
| `rating_comment` | Comment from the ticket user after attending the event. |
Great experience! |
| `rating_value` | Rating given by the ticket user after attending the event, ranging
from 1 to 5. |
5.0 |
| `surcharge` | Surcharge applied to the ticket. |
2.0 |
| `status` | If the ticket is active, transferred, or cancelled. ACTIVE:
means that the ticket ID can be redeemed or it is redeemed. CANCELLED: means that the ticket ID can't
be redeemed since it has been cancelled. TRANSFERRED: means that the ticket ID can't be used since
it has been fully transferred to another user. |
ACTIVE |
| `unitary_price` | Unitary price of the purchased ticket. |
50.0 |
| `metadata` | Partner-supplied identifiers for reconciliation against the
partner's own system of record. **Opt-in via `included_fields=metadata`.** NULL when the partner did
not provide any reporting metadata for the order item. |
_See `order_item.metadata` documentation below_ |
| `owner` | Order item owner information. |
_See `order_item.owner` documentation below_ |
| `plan_codes` | Plan code associated with the order item. |
_See `order_item.plan_codes` documentation below_ |
| `session` | Session information. |
_See `order_item.session` documentation below_ |
| `pack` | Pack information if the order item belongs to a pack. `null`
when the order item does not belong to a pack. |
_See `order_item.pack` documentation below_ |
order_item.metadata
Partner-supplied identifiers attached at the time of purchase, intended to help partners reconcile
Fever order items against rows in their own system of record (box-office ticket IDs, internal SKUs,
subproduct variants, etc.). Only present when the request opts in via `included_fields=metadata`;
NULL when the partner did not provide any reporting metadata for the order item.
| Column Name | Description |
Example value |
|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| `external_id` | Partner-supplied external identifier for the order item, as sent by the
partner's integration when the order was placed. |
CJ51001B |
| `external_subproduct_id` | Partner-supplied external subproduct identifier for the order item, used
when a single plan exposes multiple distinguishable subproducts (e.g., adult vs. child ticket variants,
add-ons, seating categories). | ADULTO |
order_item.owner
| Column Name | Description |
Example value |
|------------------------|-----------------------------------------------------------------------------------------------------------------|------------------|
| `id` | Unique ID of the person who owns the ticket. |
123456 |
| `first_name` | First name of the owner of the ticket. |
John |
| `last_name` | Last name of the owner of the ticket. |
Doe |
| `email` | Email of the owner of the ticket. |
test@example.com |
| `date_of_birthday` | Date of birth of the owner of the ticket. |
1990-01-01 |
| `marketing_preference` | Indicates whether the user accepted receiving marketing communications
from the partner in the checkout screen. | true |
| `language` | Language of the owner of the ticket, extracted from the device locale.
The format is ISO 639-1 (two letters). | en |
order_item.plan_codes
| Column Name | Description |
Example value |
|---------------------|----------------------------------------------------------------------------------------------------|----------------------|
| `id` | Unique ID of the plan code. A plan code is the unique code needed for redemption
to join an event. | 111 |
| `cd_barcode` | Barcode code associated to the plan code. |
A1B2C3 |
| `created_date_utc` | UTC date of the creation of the plan code. |
2021-01-01T00:00:00Z |
| `modified_date_utc` | UTC date of the last modification of the plan code. |
2021-01-01T00:00:00Z |
| `redeemed_date_utc` | UTC date when the plan code was redeemed. |
2021-01-01T00:00:00Z |
| `is_cancelled` | Whether the plan code is cancelled or not. |
false |
| `is_validated` | Whether the plan code has been validated or not. |
true |
order_item.session
| Column Name | Description |
Example value |
|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|
| `id` | Unique ID of the session. A session represents a specific date and
ticket type of a plan, and also the product the client purchased. | 123456 |
| `name` | Name of the session, providing a short description of the product
the client purchased. | Session Name |
| `end_date_utc` | UTC end date of the session. |
2021-01-01T00:00:00Z |
| `first_purchasable_date_utc` | UTC date of the first purchasable date of the session. |
2021-01-01T00:00:00Z |
| `is_addon` | Indicates whether the session is an addon. |
false |
| `is_wait_list` | Indicates whether the session is actually a waitlist. |
false |
| `start_date_utc` | UTC start date of the session. |
2021-01-01T00:00:00Z |
| `venue` | Venue information. |
_See `order_item.session.venue` documentation below_ |
order_item.session.venue
| Column Name | Description | Example value |
|-------------|-------------------------------------------------------------|---------------|
| `city` | City of the venue where the session takes place. | Madrid |
| `country` | Country of the venue where the session takes place in ISO3. | Spain |
| `name` | Name of the venue where the session takes place. | Venue Name |
| `timezone` | Timezone of the venue where the session takes place. | Europe/Madrid |
order_item.pack
Pack information for order items that belong to a pack. `null` when the order item does not belong
to a pack.
| Column Name | Description |
Example value |
|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| `id` | Unique identifier of the pack unit. Groups all member order items belonging to
the same purchased pack. |
11223 |
| `session_id` | Unique catalog session ID for the pack. Matches the `id` returned by `GET /v1/sessions`.
Stable across all purchases of the same pack session. Use this instead of `session_name`, which is
not unique. `null` when the item does not belong to a pack. | 284360344 |
| `session_name` | Pack session label (display name of the pack). Not unique β multiple packs across
different plans may share the same label. |
Family Pack |
humanURL: https://developer.feverup.com/en/
baseURL: https://data-reporting-api.prod.feverup.com/v1
tags:
- Order Items
properties:
- type: OpenAPI
url: openapi/fever-order-items-api-openapi.yml
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: Authentication
url: authentication/fever-authentication.yml
- aid: fever:fever-plans-api
name: Fever Plans API
description: >-
The goal of the Plan endpoint is to provide all information about the plans/events/experiences/listings
organised by a
partner. The delay of the data is less than 10 minutes from reality.
## Model documentation
π /plans response entity model
| Column Name | Description |
Example value |
|-------------------------|------------------------------------------------------------------------|-------------------------------|
| `id` | ID of the plan |
12345 |
| `name` | Name of the plan |
Plan name |
| `currency` | ISO3 currency of the plan |
EUR |
| `is_wait_list` | Indicates if the plan is a wait list |
false |
| `gallery.type` | Plan gallery resource type (e.g. image). |
image |
| `gallery.url` | Full URL of the gallery resource. |
https://example.com/image.jpg |
| `taxonomies.id` | Unique ID of the taxonomy. A taxonomy is a classification of the plan.
| 2324 |
| `taxonomies.name` | Name of the taxonomy. |
Music |
| `partner_id` | ID of the partner |
12345 |
| `partner_name` | Name of the partner |
Partner name |
| `city` | City where the plan is located |
Barcelona |
| `state` | State where the plan is located |
Catalonia |
| `venue` | Venue where the plan is located |
Wembley Stadium |
humanURL: https://developer.feverup.com/en/
baseURL: https://data-reporting-api.prod.feverup.com/v1
tags:
- Plans
properties:
- type: OpenAPI
url: openapi/fever-plans-api-openapi.yml
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: Authentication
url: authentication/fever-authentication.yml
- aid: fever:fever-sessions-api
name: Fever Sessions API
description: >-
The goal of the Session Endpoint is to provide all information about the session (or ticket types)
of a plan.
The delay of the data is less than 10 minutes from reality.
## Request filters
`POST /v1/sessions/search` accepts the following optional request body fields. Filters compose with
the existing `plan_ids` / `session_ids` OR-union behaviour: the warehouse update window is applied
as an extra `AND` constraint on top of that union.
| Field | Type | Required | Description |
|--------------------------|--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `plan_ids` | `list[int]` | no | Restrict sessions to the given
plans. Unchanged. |
| `session_ids` | `list[int]` | no | Restrict to the given sessions.
Unchanged. |
| `updated_date_utc_from` | `string` (UTC datetime) | no | **Inclusive** lower bound on the
session warehouse row's last-updated timestamp (`DT_LAST_UPDATED`). Format `YYYY-MM-DD HH:MM`; if
only the date is sent, `00:00` is appended. Must be sent together with `updated_date_utc_to`. |
| `updated_date_utc_to` | `string` (UTC datetime) | no | **Exclusive** upper bound on `DT_LAST_UPDATED`.
Same format and pairing rules as `updated_date_utc_from`. |
The applied predicate is the half-open interval `DT_LAST_UPDATED >= updated_date_utc_from AND DT_LAST_UPDATED
< updated_date_utc_to`, consistent with the cart-creation window on `/v1/carts`.
### Validation errors (`422 Unprocessable Entity`)
- Only one of `updated_date_utc_from` / `updated_date_utc_to` is provided.
- `updated_date_utc_from >= updated_date_utc_to`.
- Either bound is not a valid `YYYY-MM-DD HH:MM` (or `YYYY-MM-DD`) string.
### Example request
```json
POST /v1/sessions/search
{
"plan_ids": [12345],
"session_ids": [],
"updated_date_utc_from": "2026-05-24 00:00",
"updated_date_utc_to": "2026-05-25 00:00"
}
```
The response shape is unchanged β these filters only narrow which sessions are returned.
## Model documentation
π /sessions response entity model
| Column Name | Description |
Example value |
|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
| `id` | ID of the session |
12345 |
| `name` | Name of the session, providing a short description of the product
the client purchased. | Adult Ticket |
| `available_tickets` | Current number of available tickets for sale in the session. |
103 |
| `capacity` | Current maximum number of tickets that can afford the session
(sold + available). | 400 |
| `end_date_utc` | UTC end date of the session. |
2025-03-21 22:59:00.000 Z |
| `first_purchasable_date_utc` | UTC date of the first purchasable date of the session. |
2025-03-21 |
| `is_addon` | Indicates whether the session is an addon. |
FALSE |
| `is_wait_list` | β οΈ (_deprecated_) Indicates whether the session is actually a
waitlist. This field is deprecated, it is now configured at plan level, not at session level | FALSE |
| `plan_id` | ID of the plan associated with the session. |
12345 |
| `start_date_utc` | UTC Start date of the session. |
2025-03-21 22:59:00.000 Z |
| `venue.city` | City of the venue where the session takes place. |
Madrid |
| `venue.country` | Country of the venue where the session takes place in ISO3. |
Spain |
| `venue.name` | Name of the venue where the session takes place. |
Retiro |
| `venue.timezone` | Timezone of the venue where the session takes place. |
Europe/Madrid |
| `ticket_price` | Price of the ticket in the session. |
10 |
| `ticket_price_tax_base` | Base price of the ticket in the session. |
8 |
| `surcharge_per_ticket` | Surcharge applied to the ticket in the session. |
1 |
| `surcharge_per_ticket_tax_base` | Base price of the surcharge per ticket |
1 |
| `session_type_id` | Fever session-type identifier. Join key for `/reports/entitlements`. |
88123 |
| `product_type` | Product type of the session (e.g. `TIMED_ENTRY`). Nullable β returns
`null` when the session has no associated session type. | TIMED_ENTRY |
| `customer_profile` | Target customer profile of the session (e.g. `ADULT`, `CHILD`).
Nullable β returns `null` when the session has no associated session type. | ADULT |
| `group_name` | Name of the session type group. Nullable β returns `null` when
the session type has no associated group. | General
Admission |
humanURL: https://developer.feverup.com/en/
baseURL: https://data-reporting-api.prod.feverup.com/v1
tags:
- Sessions
properties:
- type: OpenAPI
url: openapi/fever-sessions-api-openapi.yml
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: Authentication
url: authentication/fever-authentication.yml
common:
- type: CapabilityMap
url: capabilities/fever-capability-edges.yml
name: Fever Business Capability Map
- type: Overlay
url: overlays/fever-reporting-api-overlay.yaml
- type: DeveloperPortal
url: https://developer.feverup.com/en/
- type: Documentation
url: https://developer.feverup.com/en/
- type: APIReference
url: https://data-reporting-api.prod.feverup.com/v1/redoc
- type: MCPServer
url: mcp/fever-mcp.yml
- type: WellKnown
url: well-known/fever-well-known.yml
- type: LLMsTxt
url: llms/fever-llms.txt
- type: Authentication
url: authentication/fever-authentication.yml
- type: AgenticAccess
url: agentic-access/fever-agentic-access.yml
- type: AgentSkill
url: skills/_index.yml
- type: ErrorCatalog
url: errors/fever-problem-types.yml
- type: Conventions
url: conventions/fever-conventions.yml
- type: RateLimits
url: rate-limits/fever-rate-limits.yml
- type: Lifecycle
url: lifecycle/fever-lifecycle.yml
- type: StatusPage
url: https://status.data-reporting-api.prod.feverup.com/
- type: Conformance
url: conformance/fever-conformance.yml
- type: DataModel
url: data-model/fever-data-model.yml
- type: DomainSecurity
url: security/fever-domain-security.yml
- type: Support
url: https://fever.zendesk.com/hc/en-us
- type: TermsOfService
url: https://feverup.com/legal/terms_en.html
- type: PrivacyPolicy
url: https://feverup.com/legal/privacy_en.html
- type: Website
url: https://www.feverup.com
x-enrichment:
date: '2026-07-19'
status: backfilled
pass: local-v1
note: backfilled from .gitignore signal + verified work evidence