Activity calories
API · /calorieburn-api
Calorie Burn API
Exercise calorie-burn maths as an API, computed locally and deterministically with the MET (metabolic-equivalent) method. The activity endpoint computes the calories burned by an activity, calories = MET × weight × hours, taking the MET value directly or from a named-activity table (walking, running, cycling, swimming, HIIT, rowing, yoga, weightlifting and more), and returns the calories per minute. The steps endpoint turns a step count into distance and calories: the stride is estimated from height (about 0.415 × height for walking, 0.65 for running), the distance is steps × stride, and the energy is the distance times bodyweight times a net cost of roughly 0.5 kcal/kg/km walking or 1.0 running. The duration endpoint works backwards, giving the minutes of an activity needed to burn a target number of calories. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, activity-tracking and weight-management app developers, workout and step-counter tools, and wellness dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Estimates only. 3 endpoints. This is activity energy expenditure; for resting metabolism and TDEE use a BMR API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 91 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,732
- attiva
- Chiamate totali
- 32
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 3,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 22,735 calls/month
- 2 req/sec
- Activity + steps + duration
- No credit card
Starter
€4.00 /mese
- 40,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 34.05k llamadas/mes
- 8 req/seg
- Más de 20 ajustes preestablecidos de actividad, distancia de paso
- Soporte por correo electrónico
Pro
€12.00 /mese
- 250,000 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 374.5k calls/month
- 20 req/sec
- Activity-tracking app pipelines
- Priority support
Mega
€39.00 /mese
- 1,508,000 chiamate/mese
- 60 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.915M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Met Museum API
搜尋大都會藝術博物館開放取用的47萬多件藏品,取得完整藝術品詳細資訊——藝術家、年代、媒材、文化、部門、公共領域狀態及高解析度圖片——並列出博物館各部門。非常適合藝術、教育、文化及畫廊應用程式。
api.oanor.com/museum-api
Barbell & Lifting API
Barbell- und Gewichtheber-Mathematik als API, lokal und deterministisch berechnet – die Plattenbeladungs- und Prozentzahlen, die ein Lifter, Trainer oder eine Fitness-App an der Hantelbank ausrechnet. Der Platten-Endpunkt löst das alltägliche Rätsel im Fitnessstudio, welche Platten auf jeder Seite für ein Zielgewicht aufgelegt werden müssen: 100 kg auf einer Standard-20-kg-Stange bedeuten 40 kg pro Seite, zuerst die schwersten als 25er und 15er; 102,5 kg fügt die 1,25-Mikroplatte hinzu; und wenn ein Ziel mit den vorhandenen Platten nicht erreichbar ist, lädt es die nächstmögliche Kombination und teilt das Defizit mit, sodass Sie nie raten müssen. Es funktioniert in Kilogramm oder Pfund (225 lb auf einer 45-lb-Stange sind zwei 45er pro Seite), mit einem benutzerdefinierten Stangengewicht und einem benutzerdefinierten Plattensatz. Der Prozent-Endpunkt wandelt ein One-Rep-Max in das tatsächlich zu ladende Arbeitsgewicht um: 80 % eines 100-kg-Maximums sind 80 kg, und die Abfrage eines Fünf-Wiederholungs-Gewichts ergibt etwa 85,7 kg über die Epley-Formel (1RM = Gewicht × (1 + Wiederholungen ÷ 30)) – fünf Wiederholungen liegen nahe 86 % des Maximums, zehn Wiederholungen nahe 75 %. Der Aufwärm-Endpunkt baut eine Rampe von der leeren Stange bis zum Arbeitssatz bei etwa 40, 55, 70 und 85 %, jede auf einen ladbaren Schritt gerundet, wobei die Wiederholungszahl sinkt, wenn die Stange schwerer wird. Alles wird lokal und deterministisch berechnet, also sofort und privat. Ideal für Entwickler von Fitnessstudio-, Krafttrainings-, Powerlifting- und Fitness-Apps, Workout-Logger und Coaching-Tools sowie für Entwickler von intelligenten Hantelbänken und Plattenrechnern. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Exakte Mathematik, keine Simulation. Live, nichts gespeichert. 3 Compute-Endpunkte. Für die Schätzung des One-Rep-Max aus einem Satz verwenden Sie eine Strength-API.
api.oanor.com/barbell-api
Body Fat API
Body-fat-percentage and body-composition maths as an API, computed locally and deterministically. The navy endpoint applies the US Navy circumference method — for men %BF = 495/(1.0324 − 0.19077·log10(waist − neck) + 0.15456·log10(height)) − 450, and for women a formula that adds the hip measurement — to estimate body fat from a tape measure alone, returning the percentage and the fitness category (essential, athletes, fitness, acceptable or obese); a man of 178 cm with a 40 cm neck and 90 cm waist reads about 18.7 %. The deurenberg endpoint gives the BMI-based estimate %BF = 1.20·BMI + 0.23·age − 10.8·(1 if male) − 5.4 from BMI or weight and height plus age. The composition endpoint splits a total weight into fat mass and lean (fat-free) mass from a body-fat percentage. Circumferences and height are in centimetres and weight in kilograms. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, wellness, gym, nutrition, body-tracking and health-education app developers, body-composition and progress-tracking tools, and coaching software. These are estimation formulas, not a substitute for DEXA or professional assessment. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is body-fat percentage; for body-mass index use a BMI API and for basal metabolic rate a BMR API.
api.oanor.com/bodyfat-api
Hydration Calculator API
Hydration and fluid-balance maths as an API, computed locally and deterministically. The daily endpoint estimates the daily fluid need from bodyweight (about 35 ml per kilogram), the minutes of exercise (about 12 ml per minute) and the climate (hot adds 500 ml, very hot 1000 ml, cold subtracts 200 ml), reported in millilitres, litres and 250 ml glasses. The sweat endpoint computes the sweat rate and the degree of dehydration from a before-and-after body weight, the fluid drunk and the duration — sweat loss = (pre − post) + intake − urine, with 1 kg of lost mass treated as 1 litre, and it flags when losses pass the 2 % of body mass where performance falls off. The rehydrate endpoint computes the post-exercise rehydration target, about 1.5 times the fluid deficit to cover ongoing urine losses, with a sodium note for larger losses. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, sports and wellness app developers, endurance-training and hydration-reminder tools, and health dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. General guidance, not medical advice. 3 endpoints. This is fluid balance; for basal calories use a BMR API and for heart-rate zones use a heart-rate API.
api.oanor.com/hydration-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Calorie Burn API?
Qual è il limite di velocità di Calorie Burn API?
Quanto costa Calorie Burn API?
Posso cancellare l'abbonamento in qualsiasi momento?
Calorie Burn API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/calorieburn-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/calorieburn-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/calorieburn-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/calorieburn-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.