Intervals.icu API Terms and Conditions

1

Intervals.icu API Terms and Conditions

Effective Date: October 23, 2025

These Terms and Conditions (“Terms”) govern your access to and use of the Intervals.icu API (“API”). By accessing or using the API, you agree to these Terms. If you do not agree, do not use the API.

1. License Grant

We grant you a non-exclusive, worldwide, royalty-free, perpetual license to access and use the API for any lawful purpose, including commercial use. Except for the Garmin attribution requirements in 1.1, you may integrate, modify, distribute, and sublicense outputs derived from the API without restriction or attribution.

1.1 Garmin Data Attribution

Activity data obtained through the Intervals.icu API may include data that requires attribution to Garmin. Therefore, if your application displays information derived from Garmin-sourced data, you must display attribution to Garmin in the form and manner required by Garmin’s brand guidelines.

2. Your Responsibilities

  • Comply with all applicable laws.
  • Do not use the API for illegal activities, malware distribution, or to harm others.
  • Do not abuse the API.

3. Data and Privacy

We may use aggregated, anonymised usage data to improve the service.

4. Termination

You may stop using the API anytime. We may suspend or terminate access if you violate these Terms, with 7 days’ notice where possible.

5. Disclaimers

THE API IS PROVIDED “AS IS” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

6. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING FROM API USE, EVEN IF ADVISED OF THE POSSIBILITY.

7. Changes

We may update these Terms with 30 days’ notice via email. Continued use constitutes acceptance.

8. Governing Law

These Terms are governed by the laws of South Africa, without regard to conflict of laws principles.

Contact: For questions, email support@intervals.icu. By using the API, you acknowledge you have read and agree to these Terms.

6 Likes
2

Personally I’d remove the parenthesis and write as “Except for the Garmin attribution requirements in 1.1, you may integrate, modify, distribute, and sublicense outputs derived from the API without restriction or attribution.”

3 Likes
3

If i understand the Garmin API Guidelines correctly, you need to specify when using data from garmin, like showing the garmin modell which was used to record the data. We already have that information in the activity, all good.

What about wellness data from garmin? I mean if i get wellness data from the intervals.icu api, there is no field which shows me where data came from, right?

4

Yes the wellness stuff is hard to deal with. On the /fitness page and in other similar places, Intervals.icu just has a note “Charts may include data from Garmin devices” regardless of the source of the data. It is very tricky to try figure out if there is any Garmin data there or not.

1 Like
5

Alright, that works for me.

6

Please use the “device_name” field on activity to identify data from Garmin. That will contain (ignoring case) “garmin” if the activity is from a Garmin device.

If you are uploading original fit files from Garmin Connect to Intervals.icu, the device name will extracted from the file. If you are uploading a modified file then please use the device_name query parameter or form field to specify the device name. If you know it is from Garmin but not the device, just use ‘Garmin’.

1 Like
7

Looks like I’m all set. All detailed activity Data timeline will have a field using the device_name api field.

 let pmName              = json[i]["power_meter"].stringValue
 let pmBatt              = json[i]["power_meter_battery"].stringValue
 let pmSerial            = json[i]["power_meter_serial"].stringValue
 let deviceName          = json[i]["device_name"].stringValue.trimmingCharacters(in: .whitespaces)
2 Likes