Body Fat Imperial API¶
Estimate body-fat percentage from imperial measurements with response structure aligned to the metric body-fat endpoint.
Endpoint¶
GET /api/v1/bodyfat_imperial(alias:/api/v1/bodyfat/imperial)POST /api/v1/bodyfat_imperial/post(alias:/api/v1/bodyfat/imperial/post)
Parameters¶
| Name | Type | Required | In | Description |
|---|---|---|---|---|
gender | string (male,female) | Yes | Query/Body | Biological sex. |
age | number | Yes | Query/Body | Age in years. |
height | number | Yes | Query/Body | Height in inches. |
weight | number | Yes | Query/Body | Weight in pounds. |
lang | string | No | Query | Response language (en,es,de,fr,pt,ja,hi,ar). |
Why Use This Endpoint¶
- Native US-unit body-fat estimation for faster integrations.
- Preserve parity with metric endpoint classification output.
- Improve portability across consumer and clinical products.
Request Example¶
curl -X GET "https://api.hefitapi.com/api/v1/bodyfat_imperial?gender=male&age=34&height=70&weight=181&lang=en" \
-H "X-API-Key: YOUR_API_KEY"
curl -X POST "https://api.hefitapi.com/api/v1/bodyfat_imperial/post?lang=en" \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
-d '{"gender":"male","age":34,"height":70,"weight":181}'
Response Example¶
Info
The response example below is for demonstration purposes only. Make a live request to this endpoint to receive the full, real-time, and potentially richer JSON structure.
{
"height": "5.8 ft",
"weight": "181.0 lb",
"bmi": "26.0 lb/in2",
"bodyfat": "23.26 %",
"age": 34.0,
"gender": "male",
"bodyfat_status": "Average",
"bodyfat_percent": 23.26,
"bmi_value": 25.97,
"bodyfat_band": "average",
"bodyfat_band_label": "Average",
"risk_signal": "Current profile is manageable with consistency.",
"action_plan": ["Maintain training consistency"],
"monitoring_plan": "Check body-fat trend monthly.",
"language": "en",
"_enterprise": {
"client": "Acme Health",
"plan": "pro",
"request_id": "d3f8ce6e29b7094f",
"quota": 120,
"usage_tracking": true
},
"_api_metadata_": {
"api_name": "Health Fitness API by Dakidarts®",
"endpoint_name": "bodyfat_imperial",
"response_language": "en"
}
}
Market Positioning¶
Suitable for US wellness portals and direct-to-consumer fitness apps where imperial data entry is dominant.
Note
Height must be greater than zero; the endpoint rejects invalid dimensions with HTTP 400.
Recommended Endpoints¶
GET /api/v1/bodyfat- Bodyfat APIGET /api/v1/bodyfat/army- Bodyfat Army APIGET /api/v1/bodyfat/navy- Bodyfat Navy APIGET /api/v1/ajbw_imperial- Ajbw Imperial APIGET /api/v1/bmi_imperial- Bmi Imperial APIGET /api/v1/bmi- Bmi API