Stream FightCamp data. Straight from the phone.
FightCamp is a connected home boxing system — punch trackers and a bag — and its app writes each completed workout, along with heart rate and calories, to Apple Health. Sahha’s SDK reads them into your app as normalized exercise sessions and vitals, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Boxing session
- 24 min
- Heart rate
- 148 bpm
- Active energy
- 312 kcal
Identical schema across 500+ sources
Your users connect FightCamp. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every FightCamp signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.
A Allow "your app"
On-device and permissioned
FightCamp data is read on the user’s own device, only after they grant Apple Health permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health — FightCamp today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What FightCamp syncs through Apple Health.
Request only what you need
You choose exactly which of these signals to request from Apple Health — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
FightCamp, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Workouts, heart rate, and calories pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- workoutActivityTypeexercise_session_*min
- activeEnergyBurnedactive_energy_burnedkcal
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeBoxing",
"duration": 1440,
"totalEnergyBurned": { "value": 312, "unit": "kcal" },
"sourceRevision": { "source": { "name": "FightCamp" } }
}[
{
"category": "activity",
"type": "exercise_session_boxing",
"value": 24,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T18:00:00Z",
"endDateTime": "2026-06-02T18:24:00Z"
},
{
"category": "activity",
"type": "active_energy_burned",
"value": 312,
"unit": "kcal",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T18:00:00Z",
"endDateTime": "2026-06-02T18:24:00Z"
}
]FightCamp writes the workout envelope and its physiological signals — duration, heart rate, and active energy. Punch count, output, and round-level statistics stay in the FightCamp app; they have no Apple Health equivalent, so they don’t cross. This is an Apple-Health-only integration.
Missing a metric you need? Talk to us in the Sahha Slack — if FightCamp captures it, we can usually add support.
Get more than just raw data
Sahha turns these signals into biomarkers, scores, archetypes, and insights — the modeling done for you.
Reading Apple Health yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain on iOS. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Handle iOS version differences.
- Add Health Connect separately for Android.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Request the right permissions.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of HealthKit types.
- Reconcile against your Android sources.
Deduped, typed, one schema — one stream per user.
- Build a sleep model.
- Build an activity model.
- Hire a data scientist.
Scores, archetypes, and insights — built in.
- Apple changes a HealthKit API.
- You find out in production.
We version the SDK. You never notice.
No FightCamp developer account needed — Sahha reads what FightCamp already writes to Apple Health on iOS.
Live in an afternoon, not a sprint.
- # Add the Sahha SDKnpm install sahha-react-native01
Add the Sahha SDK
Drop the Sahha SDK into your iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for Apple Health permissions
Call the SDK to show the native Apple Health consent sheet. The user chooses what to share — under your brand. It’s one prompt, ever: permission is per data type, not per brand, so every future source is already covered.
- Your app LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads FightCamp data from Apple Health in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live FightCamp data the same day they add the SDK. The only per-source prerequisite: your user has FightCamp’s Apple Health sync switched on — most source apps enable it by default.
Route it into your stack.
Sahha streams every update to your webhook — and a step-by-step guide takes it the rest of the way into your database, CDP, or messaging tool.
FightCamp integration questions
How does Sahha get FightCamp data?
The FightCamp app writes each completed workout to Apple Health, and Sahha reads it from there with its mobile SDK — so you get boxing sessions, heart rate, and calories without integrating a FightCamp API directly.
What FightCamp data does Sahha receive?
The workout itself — duration — plus the heart rate and active energy recorded during it. Those three arrive as normalized exercise sessions and vitals, in the same fields and units as every other source.
Does Sahha get punch count or output from FightCamp?
No. Punch count, output, and round-level statistics stay inside the FightCamp app — Apple Health has no field for them, so they never cross. What you get is the workout envelope and its physiological signals: duration, heart rate, and calories.
Does the FightCamp integration work on Android?
No. The write path we can confirm is Apple Health, so this is an iOS-only integration and the page doesn’t claim otherwise. Your users’ other Android sources still flow through the same Sahha SDK.
Is the FightCamp integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and FightCamp data flows through the same compliant pipeline as every other source.
One API for every other source, too.
Add another wearable or app and the schema, webhooks, and scores are identical — no new pipeline to build.
Start streaming FightCamp data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for FightCamp and every other source.
Free for 30 days · No credit card
- One API for FightCamp and every other source
- Real-time webhooks + on-demand REST, one normalized schema
- Scores, archetypes & insights — no modeling required
- HIPAA, GDPR & SOC 2 · your brand on the consent screen