Theme Park Wait Times History - Disney, Universal, 100+ Parks
Pricing
$0.30 / 1,000 wait snapshots
Live ride waits only show now. Snapshot Disney, Universal, SeaWorld, Six Flags and 100+ parks into a growing history, with a best-hour-to-ride summary per ride. Schedule it every 15-30 minutes. Powered by ThemeParks.wiki and Queue-Times.com.
You can access the Theme Park Wait Times History - Disney, Universal, 100+ Parks programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
# Set API token$API_TOKEN=<YOUR_API_TOKEN>
# Prepare Actor input$cat > input.json << 'EOF'<{< "source": "themeparks.wiki",< "parks": [< "Magic Kingdom"< ],< "maxParks": 3,< "includeClosed": false,< "historyStoreName": "theme-park-wait-history",< "historyDays": 90,< "bestHourMinSamples": 2<}<EOF
# Run the Actor using an HTTP API# See the full API reference at https://docs.apify.com/api/v2$curl "https://api.apify.com/v2/actors/that_red_bird~theme-park-wait-times-history/runs?token=$API_TOKEN" \< -X POST \< -d @input.json \< -H 'Content-Type: application/json'Below, you can find a list of relevant HTTP API endpoints for calling the Theme Park Wait Times History - Disney, Universal, 100+ Parks Actor. For this, you’ll need an Apify account. Replace <YOUR_API_TOKEN> in the URLs with your Apify API token, which you can find under API & Integrations in Apify Console. For details, see the API reference.
https://api.apify.com/v2/actors/that_red_bird~theme-park-wait-times-history/runs?token=<YOUR_API_TOKEN>Note: By adding the method=POST query parameter, this API endpoint can be called using a GET request and thus used in third-party webhooks. Please refer to our Run Actor API documentation.
https://api.apify.com/v2/actors/that_red_bird~theme-park-wait-times-history/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>Note: This endpoint supports both POST and GET request methods. However, only the POST method allows you to pass input data. For more information, please refer to our Run Actor synchronously and get dataset items API documentation.
https://api.apify.com/v2/actors/that_red_bird~theme-park-wait-times-history?token=<YOUR_API_TOKEN>For more information, please refer to our Get Actor API documentation.
Actors can be used to scrape web pages, extract data, or automate browser tasks. Use the Theme Park Wait Times History - Disney, Universal, 100+ Parks API programmatically via the Apify API.
You can choose from:
Theme Park Wait Times History - Disney, Universal, 100+ Parks API in Python
Theme Park Wait Times History - Disney, Universal, 100+ Parks API in JavaScript
Theme Park Wait Times History - Disney, Universal, 100+ Parks API through CLI
Theme Park Wait Times History - Disney, Universal, 100+ Parks OpenAPI definition
You can start Theme Park Wait Times History - Disney, Universal, 100+ Parks with the Apify API by sending an HTTP POST request to the Run Actorendpoint. An Actor’s input and its content type can be passed as a payload of the POST request, and additional options can be specified using URL query parameters. The Theme Park Wait Times History - Disney, Universal, 100+ Parks is identified within the API by its ID, which is the creator’s username and the name of the Actor.
When the Theme Park Wait Times History - Disney, Universal, 100+ Parks run finishes you can list the data from its default dataset(storage) via the API or you can preview the data directly on Apify Console.