Fever Plans API
The goal of the Plan endpoint is to provide all information about the plans/events/experiences/listings organised by apartner. 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 |
Fever Plans API is one of 5 APIs that Fever publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Plans. 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 16 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 Plans 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 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…
Schemas 16
The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are SessionDimension (22 properties), PlanDimension-Input (14 properties), PlanDimension-Output (14 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 Plans 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.