Tidepool is a 501(c)(3) nonprofit organization. We were founded by people with diabetes, caregivers, and leading healthcare providers committed to helping all people with insulin-requiring diabetes safely achieve great outcomes through more accessible, actionable, and meaningful diabetes data.
We are committed to empowering the next generation of innovations in diabetes management. We harness the power of technology to provide intuitive software products that help people with diabetes.
You can learn more about Tidepool here:
- Company
- Terms of Use
- Privacy Policy
- Security & Architecture
- Developer Portal (legacy, superseded by this site)
We strongly believe in transparency and all of our products are open source with either BSD-2 or MIT license. To that end, this site hosts two views of the Tidepool API:
- (Public) API shows the Tidepool APIs that are available to everyone. These are the APIs used by Tidepool's own customer-facing products.
- Full API shows all of Tidepool's APIs. This includes APIs that are only available between services within our AWS VPC, or require privileged access levels, or simply are not really useful for anyone outside of Tidepool. They are included here both for internal reference, but also because anyone with the time and energy can see them in our open-source software.
Tidepool is deprecating the current authentication APIs that may expose user's username and password credentials to 3rd party developers. These APIs are replaced by industry-standard OAuth2 and OpenID Connect authentication APIs. This enables Tidepool to provide a consistent and secure sign-up and sign-in user experience for all applications, including offering enterprise Single Sign-On (SSO) via external identity providers (IdP) such as Okta, Auth0, Microsoft ADFS, and so on.
We expect to fully remove the current authentication APIs by the end of 2023.
If you plan to develop software that uses Tidepool APIs, please send us an email or join our public #opensource Slack Channel. You will need to request a client identifier for your application in order to use the new authentication APIs. Make sure we know who you are so that we can keep you updated on our progress and any other upcoming API changes!
The development environments are for Tidepool's internal development use only. Do not use them at all, as they are in constant state of change and testing. There are no guarantees for privacy or stability of accounts or data.
The integration environment is for development proof-of-concept tests only. Do not use it for production data. There are no guarantees for privacy or stability of accounts or data.
To use the integration environment, you will need to create accounts on the integration environment and upload data via the integration environment. For example, before logging into the Tidepool Uploader, right click and set server to “integration”.
Once you have tested your software on the integration environment, let us know so we can review plans with you to move to our production environment.
Please do not use our production environment during your development. Only use the integration environment, or your own local back-end server environment.