07-30-2024 16:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-30-2024 16:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Fitbit team,
A user requested that we add the new scope `irn` to our integration to be able to support irregular rhythm notification alerts.
When testing the end-to-end OAuth flow, I see the following error:
"The app you're trying to connect did not provide valid information to Fitbit. Please report this issue to them. Developer information: invalid_scope - Invalid scope string : irn"
Is there something that needs to be enabled for us to add the `irn` scope?
I see that it is listed in the documentation here (https://dev.fitbit.com/build/reference/web-api/developer-guide/application-design/#Scopes)
Thanks,
Michael
Answered! Go to the Best Answer.
Accepted Solutions
08-02-2024 09:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-02-2024 09:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Awesome, retested the end-to-end flow and everything looks good now. Thanks for the update Gordon.

07-31-2024 07:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-31-2024 07:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @pipedream
Thank you for reporting this problem. Let me investigate this and I'll report back.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

07-31-2024 11:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-31-2024 11:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @pipedream
The documentation incorrect states the scope name as irn. Please change your scope name to irregular_rhythm_notifications. I will update the documentation.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
08-02-2024 09:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-02-2024 09:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Awesome, retested the end-to-end flow and everything looks good now. Thanks for the update Gordon.

