How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ThemeParks.wiki Entities API

Park entities including rides, shows, restaurants, and parks

ThemeParks.wiki Entities API is one of 2 APIs that ThemeParks.wiki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Entities. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 5 operations across 5 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.themeparks.wiki/v1.

5 operations 5 paths 8 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.themeparks.wiki/v1
Resource Areas
1

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. Each is listed below with its method, path, parameters, and response codes.

Entities 5

Park entities including rides, shows, restaurants, and parks

GET
/entity/{entityID}
ThemeParks.wiki Get Entity Details
getEntity 1 param → 200404
GET
/entity/{entityID}/children
ThemeParks.wiki Get Entity Children
getEntityChildren 1 param → 200404
GET
/entity/{entityID}/live
ThemeParks.wiki Get Live Entity Data
getEntityLiveData 1 param → 200404
GET
/entity/{entityID}/schedule
ThemeParks.wiki Get Entity Schedule
getEntitySchedule 1 param → 200404
GET
/entity/{entityID}/schedule/{year}/{month}
ThemeParks.wiki Get Entity Schedule for Specific Month
getEntityScheduleByMonth 3 params → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Entity (7 properties), LiveEntityData (7 properties), ScheduleEntry (5 properties), ScheduleResponse (4 properties). Each schema is shown below with its type and property counts.

ScheduleEntry
object
A single schedule entry for a park operating day
5 properties
QueueData
object
Queue wait time data for an attraction
1 property
Entity
object
Theme park entity (park, attraction, show, restaurant, or destination)
7 properties
ChildrenResponse
object
Entity with its children
4 properties
LiveDataResponse
object
Live data for an entity and all its children
4 properties
LiveEntityData
object
Live operational data for a single entity
7 properties
ScheduleResponse
object
Schedule for an entity
4 properties
Location
object
Geographic coordinates
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

themeparks-wiki-entities-api-openapi.yml Raw ↑

Other APIs ThemeParks.wiki publishes across the network.

ThemeParks.wiki Destinations API
Where this information came from

This is an independent, third-party profile of ThemeParks.wiki Entities 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.