Overview

You can find our claims of providing you access to more than 500+ wearables and health apps all over our website and texts. What does that mean? Find out here!

If you have made it to this page, you probably have already heard that Thryve allows developers like you to connect to all kinds of smartwatches, health trackers, consumer sensors, but also health data created from smartphones and other health apps.

Thryve Connection Widget displaying selected data sources

You can find the full list of actively supported and maintained data sources that your users can connect to. But make sure to scroll past the table, as we will explain some key concepts when it comes to consumer health data sources.

ID	Data Source	Type	Retrieval Method	Historic data	Shared oAuth-client
1	Fitbit	Web	Ping	yes	yes
2	Garmin	Web	Ping	yes	yes
3	Polar	Web	Ping	no	yes
5	Apple Health	Native	SDK	yes	n.a.
6	Samsung Health	Native	SDK	yes	n.a.
8	Withings	Web	Ping	yes	yes
11	Strava	Web	Ping	yes	yes
12	GoogleFitREST (EOL)	Web	Bulk	yes	no
16	Omron Connect	Web	Ping	yes	yes
17	Suunto	Web	Bulk	yes	yes
18	Oura	Web	Ping	yes	yes
21	iHealth	Web	Ping	yes	no
27	Beurer	Web	Bulk	yes	yes
38	HuaweiHealth	Web	Bulk	yes	yes
40	GoogleFitNative (EOL)	Native	SDK	yes	no
41	Dexcom	Web	Bulk	yes	no
42	Whoop	Web	Ping	yes	no
43	Decathlon	Web	Ping	yes	no
44	Health Connect	Native	SDK	yes	n.a.
45	Komoot	Web	Bulk	yes	no
46	FreeStyleLibre	Web	Bulk	yes	no
47	ShenAI	Native	SDK	n.a.	no

When no shared oAuth-client is available, you must bring your own oAuth-client (clientId, clientSecret) or API keys to enable the data source

You can access an overview of what data is provided by the different data sources here.