Skip to main content
Why my access tokens expire?
Support avatar
Written by Support
Updated over 2 months ago

All social media profiles will occasionally become disconnected. While your access token is invalid, you may encounter difficultietws posting scheduled content, moderating comments, and even experiencing data loss in the reports ๐Ÿฅฒ

We acknowledge that this process can be frustrating. However, it is a standard security measure implemented to ensure the safety and security of your accounts ๐Ÿ˜Ž

In such cases, you can view expired tokens in two ways:

  1. In the Control panel on the homepage, you'll see the โ€œExpired tokensโ€ part, indicating the social media profiles that need access token updates.
    โ€‹
    โ€‹

  2. Alternatively, you can check your inbox for alert emails titled "Access Token Expired: Brand Name". These emails indicate that your social media profiles need access token updates.
    โ€‹

There are multiple reasons why your access token might expire:

  • When the person who connected your pages to Sociality.io update their credentials, social media platforms revoke their access tokens to let them review their connected apps.

  • The person who connected social media accounts to the Sociality.io platform may no longer be an administrator on these accounts. Thus, your profile doesn't have access to manage the page.

  • Social media platforms periodically deactivate access tokens due to routine security checks. It is done to understand whether you haven't forgotten applications you opened access to.

Why do access tokens expire? Social media platforms and their policies can be the reason ๐Ÿ™‚

Note that regardless of the reasons and social media network, whenever your access token expires, you will need to reconnect your account to the Sociality.io platform. How? Here is a step-by-step guide for you to uncover ๐Ÿ‘‰ How can I refresh my access tokens?

Facebook and Instagram

Your Instagram and Facebook accounts, connected to Sociality.io, require more of your attention. According to Facebook, an access token typically remains valid for around 60 days. However, the exact duration of an access token is ambiguously defined, and no precise timeframe is provided.

In addition to the general reasons stated above, here are some reasons why the access token may expire.

  • You are publishing identical posts to several accounts at the same time.

  • Facebook detects many different IP addresses logging into your account. The more people have your email and password information, the more skeptical they are of the Facebook system.

  • You are often logging in and out of several different accounts.

For additional details, please check ๐Ÿ‘‰ https://developers.facebook.com/docs/facebook-login/access-tokens/

LinkedIn

LinkedIn access token requires reconnecting exactly every 60 days.

"LinkedIn offers programmatic refresh tokens that are valid for a fixed length of time. By default, access tokens are valid for 60 days, and programmatic refresh tokens are valid for a year. The member must reauthorize your application when refresh tokens expire."

In addition to regular and planned access token expiration, there are additional reasons why you may be required to reconnect your LinkedIn profile:

  • You are publishing identical posts to several LinkedIn accounts at the same time. (The social media platforms classify this behavior as spammy.)

  • You no longer have Admin access to the LinkedIn page.

YouTube

Your YouTube accounts connected to Sociality.io can also require you to reconnect your profile because of the expired token. A refresh token might stop working for one of these reasons:

  • The refresh token has not been used for six months.

  • The user changed passwords, and the refresh token contains Gmail scopes.

  • The user account has exceeded the maximum number of granted (live) refresh tokens.

  • The user belongs to a Google Cloud Platform organization that has session control policies in effect.

For additional details, please check ๐Ÿ‘‰https://developers.google.com/identity/protocols/oauth2#expiration

Did this answer your question?