Nutrition Events

In response to the growing demand for nutrition data, we launched theNutrition EventsIn this way, the extraction, transformation, and delivery of nutritional events from multiple connected health data sources can be achieved.
This improvement allows us to process nutrition information from devices like Fitbit (API) and platforms like Apple Health, Health Connect, and Samsung Health (SDKs). Thanks to this advancement, our customers will be able to access standardized nutritional data, processed and delivered according to availability or time intervals, depending on the source.
A unified approach to diverse data
With Nutrition EventsThe data structure is standardized through the new object nutrition_event
 which encapsulates key information such as:
Date and time of the event
Fuente del dato (ej. Fitbit, Apple Health, Health Connect o Samsung Health)
Nutritional indicators (calories, fats, proteins, carbohydrates, among others)
This standardization allows our partners to receive high-value information, ready for analysis or direct integration into their products.
Key features of Nutrition Events
Automated extraction via webhook (Fitbit, Android SDKs) or hourly polling (Apple Health).
Unified and validated JSON structure for all events.
Fault tolerance with automatic retries and centralized monitoring.
Compliance with security standards with internal JWT authentication.
Hourly data deliveries for aggregate sources such as Apple Health.
Driving smarter decisions
By offering precise, hourly, ready-to-use nutrition events, this launch significantly expands our customers' analytical capabilities.
Frequently Asked Questions 
How does it work?
Nutrition Events operates in two modes:
Webhook (immediate):For Fitbit, Health Connect, and Samsung Health. Each notification generates a unique event.
Polling (per hour):for Apple Health. The accumulated total is transformed into hourly deltas for each event.
The data is structured in a JSON object of typenutrition_eventwhich includes indicators such as calories, protein, fat, carbohydrates and more, plus metadata such as source, timestamp and physical activity.
What data does a nutrition event include?
Each nutrition_event
 It may include the following indicators:
data = {
	"created_at": datetime,
	"auto_detected": bool,
	"client_uuid": str,
	"user_id": str,
	"datetime": str,
	"sources_of_data": str,
	"was_the_user_under_physical_activity": bool, # Default: False
	"food_intake_number": float | None,
	"calories_intake_number": float | None,
	"protein_intake_g_number": float | None,
	"sugar_intake_g_number": float | None,
	"fat_intake_g_number": float | None,
	"trans_fat_intake_g_number": float | None,
	"carbohydrates_intake_g_number": float | None,
	"fiber_intake_g_number": float | None,
	"alcohol_intake_g_number": float | None,
	"sodium_intake_mg_number": float | None,
	"cholesterol_intake_mg_number": float | None,
	"non_structured_data": list
}
How is the data delivered?
Events are delivered via webhook to client systems. In the case of Apple Health, events are grouped and delivered hourly with their corresponding deltas, preventing accumulation. Zero values are explicitly included; no values are stored null
.
Does this product replace something that already exists?
No. It's a new data structure. Nutrition Events expands the scope of our platform to include food intake data.
How do I access this feature?
Nutrition Events is available to all customers with active integrations with supported sources (Fitbit, Apple Health, Health Connect, Samsung Health). No additional integration is required, but webhook endpoint configuration is necessary.