The Copper Mountain Data API is designed to extract and serve data about ski lifts at Copper Mountain. The API provides endpoints corresponding to each column of information in the dataset (lift name, type, capacity, length, and elevation). Users can query the dataset in a flexible way by filtering or sorting based on specific parameters like capacity ranges or lift types. This approach supports granular data exploration, making it ideal for planning visits, analyzing resort features, or comparing lifts. By avoiding the retrieval of all data in one request, the API enhances performance and usability.
{"lifts":[{"lift_type":"Combined installation (gondola and chair)","count":1},{"lift_type":"6 pers. high speed chairlift (detachable)","count":5},{"lift_type":"4 pers. high speed chairlift (detachable)","count":3},{"lift_type":"3 pers. chairlift (fixed-grip)","count":7},{"lift_type":"2 pers. chairlift (fixed-grip)","count":4},{"lift_type":"T-bar","count":1},{"lift_type":"J-bar","count":3},{"lift_type":"People mover\/Moving Carpet","count":5}]}
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8099/get+ski+lift+types' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"lift_name":"Storm King","lift_type":"T-bar","manufacturer":"Doppelmayr","ski_resort":"Copper Mountain"}
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8100/get+ski+lifts+by+type' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"lift_id":"Required"}'
[{"lift_name":"Storm King","lift_type":"T-bar","carrying_capacity_per_hour":978}]
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8101/get+ski+lift+capacity+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"lift_name":"Required"}'
{"lift_name":"Storm King","lift_type":"T-bar","length":"620 m","elevation":"978"}
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8102/get+ski+lifts+lenght+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"lift_name":"Required"}'
{"lift_name":"Storm King","lift_type":"T-bar","status":"open"}
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8103/get+ski+lift+status+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"lift_name":"Required"}'
[{"resort_name":"Copper Mountain","open_slopes":"123 of 126 km","open_ski_lifts":"24 of 24","mountain_snow_depth":"135 cm","base_snow_depth":"45 cm"}]
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8104/get+daily+snow+reports' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[{"Copper_Mountain_Season_Passes":{"Child_5-12":{"Price":429,"Valid_for":"2024-2025","Price_expires":"May 11, 2025"}}}]
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8105/get+lift+tickets+pricing' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"type":"Required","age group":"Required"}'
[{"current_temperature":"6 F\u00b0","weather_condition":"Cloudy","wind_speed":"7 m\/h","hourly_forecast":[{"day":"Today","high":"12 F\u00b0","low":"-15 F\u00b0","precipitation":"0.6\""},{"day":"Tomorrow","high":"12 F\u00b0","low":"-16 F\u00b0","precipitation":"0\""},{"day":"Friday","high":"29 F\u00b0","low":"-11 F\u00b0","precipitation":"1\""},{"day":"Saturday","high":"28 F\u00b0","low":"6 F\u00b0","precipitation":"1\""},{"day":"Sunday","high":"29 F\u00b0","low":"-2 F\u00b0","precipitation":"0\""},{"day":"Monday","high":"33 F\u00b0","low":"-3 F\u00b0","precipitation":"0\""},{"day":"Tuesday","high":"26 F\u00b0","low":"-2 F\u00b0","precipitation":"0\""}]}]
curl --location --request POST 'https://zylalabs.com/api/6023/copper+mountain+data+api/8106/get+copper+mountain+weather' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"mountain location":"Required"}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
You can filter the data by using specific parameters such as capacity ranges or lift types. This allows for more granular data exploration tailored to your needs.
By avoiding the retrieval of all data in one request, the API enhances performance and usability, allowing users to query only the specific information they need.
Yes, the API is ideal for comparing lifts as it allows users to query and analyze specific features of the lifts, making it easier to plan visits and understand resort offerings.
The Copper Mountain Data API provides structured access to various data about ski lifts, including lift names, types, capacities, lengths, and elevation. Users can query this data through specific endpoints and filter or sort based on parameters like capacity ranges or lift types.
Each endpoint returns specific data related to ski lifts at Copper Mountain. For example, the "get ski lift types" endpoint returns lift types and their counts, while the "get ski lifts by type" endpoint provides details like lift name, type, and manufacturer.
Key fields vary by endpoint. For instance, "get ski lift status by name" returns fields like lift name, type, and status, while "get daily snow reports" includes resort name, open slopes, and snow depth.
Parameters vary by endpoint. For example, "get ski lifts by type" requires a lift ID, while "get ski lift capacity by name" needs a lift name. Users can customize requests based on these required parameters.
Response data is structured in JSON format, typically as an array of objects. Each object contains relevant fields, such as lift details or snow report data, making it easy to parse and utilize programmatically.
Each endpoint provides distinct information. For example, "get lift tickets pricing" offers ticket prices by type and age group, while "get copper mountain weather" provides weather conditions, including temperature and wind speed.
Users can utilize the returned data by parsing the JSON responses to extract relevant information. For instance, they can analyze lift capacities or compare snow conditions to plan their skiing trips effectively.
Typical use cases include planning ski trips, analyzing lift features, checking current snow conditions, and comparing lift types to enhance the skiing experience at Copper Mountain.
Data accuracy is maintained through regular updates and quality checks by the Copper Mountain team. This ensures that users receive reliable and up-to-date information about ski lifts and conditions.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
4,139ms
Service Level:
100%
Response Time:
447ms
Service Level:
100%
Response Time:
528ms
Service Level:
100%
Response Time:
852ms
Service Level:
100%
Response Time:
728ms
Service Level:
100%
Response Time:
704ms
Service Level:
100%
Response Time:
1,938ms
Service Level:
100%
Response Time:
1,440ms
Service Level:
100%
Response Time:
8,515ms
Service Level:
100%
Response Time:
377ms