Calories Calculator API

This API allows users to calculate the number of calories they have burned during physical activity.

About the API:

Calories Calculator API is designed to help people track their calorie expenditure and meet their weight loss or fitness goals.

To use Calories burned API, users must enter the activity they have performed, also they can use their weight and duration of the activity/sport. The the API then uses this information to calculate an estimate of the number of calories burned.

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

It will receive a parameter and provide you with a JSON. Also, it has 2 optional parameters.

What are the most common uses cases of this API?

Tracking calorie expenditure for weight loss: Calories Calculator API can help people who are trying to lose weight by allowing them to track the number of calories they burn through physical activity. This information can be used to help them create a calorie deficit, which is necessary for weight loss.

Monitoring and improving physical fitness: It may help people monitor their physical fitness over time by tracking the number of calories they burn during different activities. This information can be used to identify areas for improvement and to track progress toward fitness goals.

Comparing the calorie burn of different activities: The API can be used to allow users to compare the calorie burn of different activities, which can be useful for people who are looking to find the most efficient ways to burn calories.

Improving athletic performance: Athletes may use Calories Calculator API to track the number of calories they burn during training and competition, in order to optimize their performance.

Are there any limitations to your plans?

Basic Plan: 5,000 API Calls.

Pro Plan: 25,000 API Calls.

Pro Plus Plan: 100,000 API Calls.

Elite Plan: 300,000 API Calls.

API Documentation

Endpoints


The "Calories Calculator" endpoint allows users to calculate the number of calories lost by making a specific sport/activity. Also, the user can provide his weight and time performing the activity in order to calculate it.

Required Parameter:

activity // This parameter allows partial matches. For example, tennis will match Table Tennis and Playing Tennis.

Optional Parameters: 

weight // The weight of the user performing the activity must be specified in pounds. The allowed range is from 50 to 500, with a default value of 160.

duration // The duration of the activity/sport must be specified in minutes. The allowed minimum value is 1. The default value is 60 minutes (1 hour).



                                                                            
GET https://zylalabs.com/api/912/calories+calculator+api/725/calories+calculator
                                                                            
                                                                        

Calories Calculator - Endpoint Features

Object Description
activity [Required] Enter the desired activity: For example: tennis
weight [Optional] The weight of the user performing the activity must be specified in pounds. The allowed range is from 50 to 500, with a default value of 160.
duration [Optional] The duration of the activity/sport must be specified in minutes. The allowed minimum value is 1. The default value is 60 minutes (1 hour).
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [{"name": "Coaching: football, basketball, soccer\u2026", "calories_per_hour": 290, "duration_minutes": 60, "total_calories": 290}, {"name": "Football, competitive", "calories_per_hour": 653, "duration_minutes": 60, "total_calories": 653}, {"name": "Football, touch, flag, general", "calories_per_hour": 581, "duration_minutes": 60, "total_calories": 581}, {"name": "Football or baseball, playing catch", "calories_per_hour": 181, "duration_minutes": 60, "total_calories": 181}]
                                                                                                                                                                                                                    
                                                                                                    

Calories Calculator - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/912/calories+calculator+api/725/calories+calculator?activity=tennis' --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 Calories Calculator 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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

πŸš€ 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

Calories Calculator API FAQs

The API returns a JSON array containing information about various activities, including the name of the activity, calories burned per hour, duration in minutes, and total calories burned based on user input.

The key fields in the response include "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).

The endpoint accepts three parameters: "activity" (required), "weight" (optional, in pounds), and "duration" (optional, in minutes). Users can customize their requests by specifying these parameters to tailor the calorie calculation.

The response data is organized as a JSON array of objects, each representing an activity. Each object contains fields for the activity name, calories burned per hour, duration, and total calories, allowing users to easily interpret the results.

The API provides information on calorie expenditure for various physical activities, allowing users to track their calorie burn based on the activity type, duration, and user weight, which aids in fitness and weight loss goals.

Users can analyze the returned data to compare calorie burn across different activities, track their progress over time, and adjust their fitness routines based on the total calories burned during specific activities.

The data is derived from established metabolic equivalents (METs) for various activities, which are widely recognized in exercise science to estimate calorie expenditure based on activity type and intensity.

If the API returns partial or empty results, users should verify the activity name for accuracy or try different variations. The API supports partial matches, so using broader terms may yield more results.

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