Fever Sessions API
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`.- Either bound is not a valid `YYYY-MM-DD HH:MM` (or `YYYY-MM-DD`) string.### Example request```jsonPOST /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 |
Fever Sessions API is one of 5 APIs that Fever publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 2 operations across 2 paths, and defines 9 schemas. It is described by OpenAPI 3.0.0, at version 1.5.0.
Requests are made against a single base URL, /v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Fever Sessions API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (OAuth2PasswordBearer) using the password flow.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
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 f…
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are SessionDimension (22 properties), Venue (4 properties), SessionsParams (4 properties), PartitionInfo (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Fever 4
Other APIs Fever publishes across the network.
This is an independent, third-party profile of Fever Sessions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.