Issue with 3-Legged Authentication – Users Unable to Verify Accounts

[Александр Полелюк]

Dear FatSecret Support Team,

I am currently developing a Telegram bot that integrates with FatSecret as one of its features, allowing users to link their FatSecret accounts to the bot.

For authentication, I implemented FatSecret’s 3-Legged Authentication flow. The integration works correctly for some users. However, several users are experiencing issues during the login process.

Specifically, when they attempt to log in using their email and password, they receive the following error message:

"Account not verified yet. Please follow the link in your email."

The problem is that no verification email is received. Users have carefully checked all folders, including Spam and Promotions, but there is no email from FatSecret. This has occurred in multiple cases, so it does not appear to be an isolated incident.

I have attached a video demonstrating the full authentication flow for reference.

Could you please help clarify:

1. Why these accounts are flagged as “not verified”?

2. Whether there is a known issue with verification emails not being delivered?

3. If there is any way to manually trigger or resend the verification email?

Please let me know if you need additional information such as specific user IDs, timestamps, or request logs.

Thank you in advance for your assistance.

[Александр Полелюк]

Can anyone help me please?

[seba...@fatsecret.com]

Thanks for reaching out. For users that experience this, can they please try and reset their fatsecret password and then try again?

On Wednesday, March 4, 2026 at 8:30:27 AM UTC+11 aleksandr...@gmail.com wrote:

Can anyone help me please?

[seba...@fatsecret.com]

Also, you are welcome to send us any user email addresses or account names to our support team here then we can investigate their user status individually and verify their accounts:

https://platform.fatsecret.com/contact

[Александр Полелюк]

Thank you for the suggestion. I have submitted the affected user email address through the support form so your team can investigate their account status individually.

However, I would also like to understand whether there is a way to prevent this issue from occurring in the future.

Since the authentication flow is part of a Telegram bot integration using FatSecret’s 3-Legged Authentication, situations where users cannot log in due to an unverified account (while also not receiving the verification email) create a blocking experience for them.

Could you please clarify:

What conditions cause an account to be marked as “not verified” in this context?

Why verification emails might not be delivered to some users?

Whether there is any recommended way for third-party integrations to handle or avoid this scenario?

Understanding the underlying cause would help us design a more reliable user flow and reduce support issues for our users.

Thank you again for your help.

среда, 4 марта 2026 г. в 02:56:28 UTC+2, seba...@fatsecret.com:

[Александр Полелюк]

Thank you for your response.

For some users, this did resolve the issue and they were able to successfully authenticate afterward.

However, for other users the problem still persists. Even after resetting their password, they continue to receive the same message:

"Account not verified yet. Please follow the link in your email."

And again, no verification email is received in their inbox (including Spam and other folders).

Is there any additional step we can recommend to users, or could this be related to specific account states on your side?

Thank you again for your assistance.

среда, 4 марта 2026 г. в 00:09:26 UTC+2, seba...@fatsecret.com:

[seba...@fatsecret.com]

Thanks for following up and elaborating.

Our team will try and look into this in the coming weeks. We can see that a small number of new users registering are not receiving their confirmation email address which is often related to users' email inboxes being out of storage.

We will further assess how this can be mitigated for 3 legged OAuth integrations.

In the interim, feel free to send through any of these user's account names and/or email addresses and we will handle these internally