# Fever FeverZone API **Canonical:** https://apis.io/apis/fever/fever-feverzone-api/ **Provider:** Fever β€” https://apis.io/providers/fever/ **Base URL:** https://data-reporting-api.prod.feverup.com/v1 **Documentation:** https://developer.feverup.com/en/ Fever FeverZone API is one of 5 APIs that [Fever](https://apis.io/providers/fever/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include FeverZone. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs. 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 |
## Machine-readable artifacts (4) - **OpenAPI** β€” https://raw.githubusercontent.com/api-evangelist/fever/refs/heads/main/openapi/fever-feverzone-api-openapi.yml - **Documentation** β€” https://developer.feverup.com/en/ - **APIReference** β€” https://data-reporting-api.prod.feverup.com/v1/redoc - **Authentication** β€” https://raw.githubusercontent.com/api-evangelist/fever/refs/heads/main/authentication/fever-authentication.yml ## Other Fever APIs (4) - [Fever Authentication API](https://apis.io/apis/fever/fever-authentication-api/) - [Fever Order Items API](https://apis.io/apis/fever/fever-order-items-api/) - [Fever Plans API](https://apis.io/apis/fever/fever-plans-api/) - [Fever Sessions API](https://apis.io/apis/fever/fever-sessions-api/) ## Tags FeverZone --- Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/fever/fever-feverzone-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/fever/.