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.
It will receive a parameter and provide you with a JSON. Also, it has 2 optional parameters.
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.
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.
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).
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). |
[{"name": "Table tennis, ping pong", "calories_per_hour": 290, "duration_minutes": 60, "total_calories": 290}, {"name": "Playing tennis", "calories_per_hour": 508, "duration_minutes": 60, "total_calories": 508}]
curl --location --request GET 'https://zylalabs.com/api/912/calories+calculator+api/725/calories+calculator?activity=tennis' --header 'Authorization: Bearer YOUR_API_KEY'
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.
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.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. 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 with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
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.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
576ms
Service Level:
100%
Response Time:
4,774ms
Service Level:
100%
Response Time:
1,085ms
Service Level:
100%
Response Time:
291ms
Service Level:
100%
Response Time:
500ms
Service Level:
100%
Response Time:
261ms
Service Level:
100%
Response Time:
1,034ms
Service Level:
100%
Response Time:
349ms
Service Level:
100%
Response Time:
568ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
126ms
Service Level:
100%
Response Time:
138ms
Service Level:
100%
Response Time:
201ms
Service Level:
100%
Response Time:
286ms
Service Level:
100%
Response Time:
410ms
Service Level:
100%
Response Time:
709ms
Service Level:
100%
Response Time:
237ms
Service Level:
100%
Response Time:
467ms
Service Level:
96%
Response Time:
1,951ms
Service Level:
100%
Response Time:
697ms
Service Level:
100%
Response Time:
322ms
Service Level:
100%
Response Time:
1,580ms
Service Level:
100%
Response Time:
3,826ms
Service Level:
100%
Response Time:
1,742ms
Service Level:
100%
Response Time:
769ms
Service Level:
100%
Response Time:
1,780ms
Service Level:
100%
Response Time:
11,372ms
Service Level:
100%
Response Time:
447ms
Service Level:
100%
Response Time:
344ms
Service Level:
100%
Response Time:
136ms
Service Level:
100%
Response Time:
996ms
Service Level:
100%
Response Time:
452ms
Service Level:
100%
Response Time:
1,123ms
Service Level:
100%
Response Time:
755ms