Burned Calories Counter API

Embark on a fitness odyssey with the Burned Calories Counter API – your guide to unraveling the secrets of your workout. Dive into a realm of precision as it calculates calories burned in diverse sports and activities. Customize weight and duration for a personalized calorie-burning adventure, transforming every exercise into a fitness masterpiece.

About the API:  

Embark on a revolutionary fitness exploration with the Burned Calories Counter API, your ultimate companion in the quest for a healthier lifestyle. This cutting-edge API seamlessly integrates into your application, providing a comprehensive solution to track and calculate the total calories burned across a diverse array of sports and activities.

Gone are the days of generic calorie estimations; the Burned Calories Counter API empowers users to tailor results to their unique profiles. Whether you're lifting weights, practicing yoga, or engaging in a game of soccer, this API accommodates your custom weight and duration preferences, ensuring unparalleled accuracy in calorie calculations.

Delve into a vast database that spans hundreds of sports and activities, from mainstream workouts to niche exercises. TheBurned Calories Counter API leverages this extensive repository to deliver precise results, catering to the diversity of fitness enthusiasts. Developers can seamlessly integrate this API into fitness apps, wearables, or health platforms, enhancing user experience by providing real-time, personalized insights.

Incorporating state-of-the-art algorithms, the API guarantees reliability in calorie computation, making it an indispensable tool for health-conscious individuals, fitness professionals, and app developers alike. Elevate your fitness application with the Lost Calories Calculator API and empower users to unravel the mysteries of their calorie-burning endeavors.



What this API receives and what your API provides (input/output)?

Returns the calories burned per hour and total calories burned according to given parameters for given activities (up to 10).

 

What are the most common use cases of this API?

  1. Personalized Fitness Tracking App: Integrate the Burned Calories Counter API into a fitness app to offer users personalized calorie tracking. Allow users to input their weight, specify activity duration, and receive accurate insights into calories burned during a wide range of sports and activities, fostering a tailored fitness experience.

  2. Workout Planning Platform: Develop a workout planning platform that leverages the Burned Calories Counter API to assist users in creating effective fitness routines. Enable users to customize their workouts based on desired calorie burn, helping them achieve fitness goals by incorporating activities that align with their energy expenditure targets.

  3. Health and Wellness Wearables: Integrate the API into health and wellness wearables to provide real-time feedback on calories burned during various physical activities. Wearable users can receive instant, accurate data, enhancing their awareness of their exercise intensity and contributing to a more informed and effective fitness routine.

  4. Corporate Wellness Programs: Employ the Burned Calories Counter API in corporate wellness programs to promote employee health. Create challenges or fitness competitions within the workplace, allowing employees to track their calorie burn in different activities. Encourage a healthy and active lifestyle by providing personalized fitness insights.

  5. Nutrition and Calorie-Tracking Apps: Enhance nutrition and calorie-tracking applications by integrating the Burned Calories Counter API. Users can seamlessly link their exercise routines to their nutritional profiles, gaining a holistic view of their daily energy balance. This integration helps users make informed decisions about their diet and exercise, fostering a comprehensive approach to health and fitness.

 

Are there any limitations to your plans?

Besides the number of API calls, there are no other limitations.

API Documentation

Endpoints


Returns the full list of activities supported by this API.

 


                                                                            
GET https://zylalabs.com/api/3437/burned+calories+counter+api/3740/activities
                                                                            
                                                                        

Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"activities": ["Cycling, mountain bike, bmx", "Cycling, <10 mph, leisure bicycling", "Cycling, >20 mph, racing", "Cycling, 10-11.9 mph, light", "Cycling, 12-13.9 mph, moderate", "Cycling, 14-15.9 mph, vigorous", "Cycling, 16-19 mph, very fast, racing", "Unicycling", "Stationary cycling, very light", "Stationary cycling, light", "Stationary cycling, moderate", "Stationary cycling, vigorous", "Stationary cycling, very vigorous", "Calisthenics, vigorous, pushups, situps\u2026", "Calisthenics, light", "Circuit training, minimal rest", "Weight lifting, body building, vigorous", "Weight lifting, light workout", "Health club exercise", "Stair machine", "Rowing machine, light", "Rowing machine, moderate", "Rowing machine, vigorous", "Rowing machine, very vigorous", "Ski machine", "Aerobics, low impact", "Aerobics, high impact", "Aerobics, step aerobics", "Aerobics, general", "Jazzercise", "Stretching, hatha yoga", "Mild stretching", "Instructing aerobic class", "Water aerobics", "Ballet, twist, jazz, tap", "Ballroom dancing, slow", "Ballroom dancing, fast", "Running, 5 mph (12 minute mile)", "Running, 5.2 mph (11.5 minute mile)", "Running, 6 mph (10 min mile)", "Running, 6.7 mph (9 min mile)", "Running, 7 mph (8.5 min mile)", "Running, 7.5mph (8 min mile)", "Running, 8 mph (7.5 min mile)", "Running, 8.6 mph (7 min mile)", "Running, 9 mph (6.5 min mile)", "Running, 10 mph (6 min mile)", "Running, 10.9 mph (5.5 min mile)", "Running, cross country", "Running, general", "Running, on a track, team practice", "Running, stairs, up", "Track and field (shot, discus)", "Track and field (high jump, pole vault)", "Track and field (hurdles)", "Archery", "Badminton", "Basketball game, competitive", "Playing basketball, non game", "Basketball, officiating", "Basketball, shooting baskets", "Basketball, wheelchair", "Running, training, pushing wheelchair", "Billiards", "Bowling", "Boxing, in ring", "Boxing, punching bag", "Boxing, sparring", "Coaching: football, basketball, soccer\u2026", "Cricket (batting, bowling)", "Croquet", "Curling", "Darts (wall or lawn)", "Fencing", "Football, competitive", "Football, touch, flag, general", "Football or baseball, playing catch", "Frisbee playing, general", "Frisbee, ultimate frisbee", "Golf, general", "Golf, walking and carrying clubs", "Golf, driving range", "Golf, miniature golf", "Golf, walking and pulling clubs", "Golf, using power cart", "Gymnastics", "Hacky sack", "Handball", "Handball, team", "Hockey, field hockey", "Hockey, ice hockey", "Riding a horse, general", "Horesback riding, saddling horse", "Horseback riding, grooming horse", "Horseback riding, trotting", "Horseback riding, walking", "Horse racing, galloping", "Horse grooming, moderate", "Horseshoe pitching", "Jai alai", "Martial arts, judo, karate, jujitsu", "Martial arts, kick boxing", "Martial arts, tae kwan do", "Krav maga training", "Juggling", "Kickball", "Lacrosse", "Orienteering", "Playing paddleball", "Paddleball, competitive", "Polo", "Racquetball, competitive", "Playing racquetball", "Rock climbing, ascending rock", "Rock climbing, rappelling", "Jumping rope, fast", "Jumping rope, moderate", "Jumping rope, slow", "Rugby", "Shuffleboard, lawn bowling", "Skateboarding", "Roller skating", "Roller blading, in-line skating", "Sky diving", "Soccer, competitive", "Playing soccer", "Softball or baseball", "Softball, officiating", "Softball, pitching", "Squash", "Table tennis, ping pong", "Tai chi", "Playing tennis", "Tennis, doubles", "Tennis, singles", "Trampoline", "Volleyball, competitive", "Playing volleyball", "Volleyball, beach", "Wrestling", "Wallyball", "Backpacking, Hiking with pack", "Carrying infant, level ground", "Carrying infant, upstairs", "Carrying 16 to 24 lbs, upstairs", "Carrying 25 to 49 lbs, upstairs", "Standing, playing with children, light", "Walk/run, playing with children, moderate", "Walk/run, playing with children, vigorous", "Carrying small children", "Loading, unloading car", "Climbing hills, carrying up to 9 lbs", "Climbing hills, carrying 10 to 20 lb", "Climbing hills, carrying 21 to 42 lb", "Climbing hills, carrying over 42 lb", "Walking downstairs", "Hiking, cross country", "Bird watching", "Marching, rapidly, military", "Children's games, hopscotch, dodgeball", "Pushing stroller or walking with children", "Pushing a wheelchair", "Race walking", "Rock climbing, mountain climbing", "Walking using crutches", "Walking the dog", "Walking, under 2.0 mph, very slow", "Walking 2.0 mph, slow", "Walking 2.5 mph", "Walking 3.0 mph, moderate", "Walking 3.5 mph, brisk pace", "Walking 3.5 mph, uphill", "Walking 4.0 mph, very brisk", "Walking 4.5 mph", "Walking 5.0 mph", "Boating, power, speed boat", "Canoeing, camping trip", "Canoeing, rowing, light", "Canoeing, rowing, moderate", "Canoeing, rowing, vigorous", "Crew, sculling, rowing, competition", "Kayaking", "Paddle boat", "Windsurfing, sailing", "Sailing, competition", "Sailing, yachting, ocean sailing", "Skiing, water skiing", "Ski mobiling", "Skin diving, fast", "Skin diving, moderate", "Skin diving, scuba diving", "Snorkeling", "Surfing, body surfing or board surfing", "Whitewater rafting, kayaking, canoeing", "Swimming laps, freestyle, fast", "Swimming laps, freestyle, slow", "Swimming backstroke", "Swimming breaststroke", "Swimming butterfly", "Swimming leisurely, not laps", "Swimming sidestroke", "Swimming synchronized", "Swimming, treading water, fast, vigorous", "Swimming, treading water, moderate", "Water aerobics, water calisthenics", "Water polo", "Water volleyball", "Water jogging", "Diving, springboard or platform", "Ice skating, < 9 mph", "Ice skating, average speed", "Ice skating, rapidly", "Speed skating, ice, competitive", "Cross country snow skiing, slow", "Cross country skiing, moderate", "Cross country skiing, vigorous", "Cross country skiing, racing", "Cross country skiing, uphill", "Snow skiing, downhill skiing, light", "Downhill snow skiing, moderate", "Downhill snow skiing, racing", "Sledding, tobagganing, luge", "Snow shoeing", "Snowmobiling", "General housework", "Cleaning gutters", "Painting", "Sit, playing with animals", "Walk / run, playing with animals", "Bathing dog", "Mowing lawn, walk, power mower", "Mowing lawn, riding mower", "Walking, snow blower", "Riding, snow blower", "Shoveling snow by hand", "Raking lawn", "Gardening, general", "Bagging grass, leaves", "Watering lawn or garden", "Weeding, cultivating garden", "Carpentry, general", "Carrying heavy loads", "Carrying moderate loads upstairs", "General cleaning", "Cleaning, dusting", "Taking out trash", "Walking, pushing a wheelchair", "Teach physical education,exercise class", "Teach exercise classes (& participate)"]}
                                                                                                                                                                                                                    
                                                                                                    

Activities - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/3437/burned+calories+counter+api/3740/activities' --header 'Authorization: Bearer YOUR_API_KEY' 


    

Returns the calories burned per hour and total calories burned according to given parameters for given activities (up to 10).



                                                                            
GET https://zylalabs.com/api/3437/burned+calories+counter+api/3741/lost+calories
                                                                            
                                                                        

Lost Calories - Endpoint Features

Object Description
activity [Required] name of the given activity. This value can be partial (e.g. ski will match water skiing and downhill skiing)
weight [Optional] weight of the user performing the activity in pounds. Must be between 50 and 500. Default value is 160.
duration [Optional] how long the activity was performed in minutes. Must be 1 or greater. Default value is 60 (1 hour).
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [{"name": "Stretching, hatha yoga", "calories_per_hour": 308, "duration_minutes": 20, "total_calories": 102}, {"name": "Mild stretching", "calories_per_hour": 193, "duration_minutes": 20, "total_calories": 64}]
                                                                                                                                                                                                                    
                                                                                                    

Lost Calories - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/3437/burned+calories+counter+api/3741/lost+calories?activity=skiing' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Burned Calories Counter API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Burned Calories Counter API FAQs

he API employs advanced algorithms based on metabolic equivalents (METs) and specific activity data to accurately estimate calories burned during various sports and activities.

Yes, the API supports customizable weight and duration inputs, ensuring precise calorie estimations tailored to individual user profiles and activity durations.

The API boasts a comprehensive database covering hundreds of sports and activities, ranging from mainstream workouts to specialized exercises, providing versatility in fitness tracking.

Developers can integrate the API using RESTful endpoints, making HTTP requests to access calorie calculation functionalities. Detailed documentation with examples is provided for a seamless integration process.

Yes, the API can support real-time tracking, allowing users to receive instant feedback on calories burned during ongoing physical activities, making it suitable for live fitness applications and wearables.

The GET Activities endpoint returns a comprehensive list of supported sports and activities. The data includes various types of exercises, categorized by intensity and type, allowing users to select from a wide range of options for calorie calculations.

The GET Lost Calories endpoint response includes key fields such as "name" (activity name), "calories_per_hour" (calories burned per hour), "duration_minutes" (duration of the activity), and "total_calories" (calories burned during the specified duration).

Users can customize their requests by specifying parameters such as weight, duration, and the type of activity (up to 10 activities). This allows for tailored calorie calculations based on individual profiles and exercise routines.

The response data from the GET Lost Calories endpoint is organized as an array of objects, each representing a specific activity. Each object contains fields for activity name, calories burned per hour, duration, and total calories burned, making it easy to interpret.

The GET Activities endpoint provides information on various sports and activities, including their names and categories. This allows users to explore different exercise options and select the most relevant activities for their calorie tracking needs.

Data accuracy is maintained through the use of established metabolic equivalents (METs) and validated activity data. The API employs state-of-the-art algorithms to ensure reliable calorie calculations across a diverse range of sports and activities.

Typical use cases include personalized fitness tracking, workout planning, and integration into health and wellness wearables. Users can leverage the data to monitor their calorie expenditure during various activities, helping them achieve fitness goals.

Users can utilize the returned data to assess their calorie burn for specific activities, adjust their workout intensity, and plan their fitness routines. By analyzing total calories burned, users can make informed decisions about their exercise and dietary habits.

General FAQs

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 1,000 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 1,000 requests per month, this header will display 1,000.

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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs


You might also like