anonymous_session | Community
Skip to main content
Answered

anonymous_session

  • January 20, 2026
  • 1 reply
  • 79 views
A

There is a property that the SDK adds to requests to Intercom. It is called anonymous_session . It appears to keep the API calls to Intercom working beyond the JWT expiry. :

  1. Why does this keep authentication alive?
  2. Is there a way we can disable it to have more control over the amount of time the API is accessible.

Best answer by Dara K

Hey ​@Amitav Singh, the SDK sends a parameter called anonymous_session. That value is a separate session token (not the JWT). When the JWT expires, our API can still recognize the user using this anonymous session, so requests keep working until that session expires (by default up to 7 days, and it can be extended). So “authentication” stays alive because we’re still identifying the user via the anonymous session, not by refreshing the JWT.

If you want to disable this please send me the App ID for your Workspace and I can opt you in to a feature flag that will disable anonymous_session.

    1 reply

    D
    Intercom Team
    Forum|alt.badge.img+1
    • Dara KIntercom Team
    • Intercom Team
    • Answer
    • January 30, 2026

    Hey ​@Amitav Singh, the SDK sends a parameter called anonymous_session. That value is a separate session token (not the JWT). When the JWT expires, our API can still recognize the user using this anonymous session, so requests keep working until that session expires (by default up to 7 days, and it can be extended). So “authentication” stays alive because we’re still identifying the user via the anonymous session, not by refreshing the JWT.

    If you want to disable this please send me the App ID for your Workspace and I can opt you in to a feature flag that will disable anonymous_session.

    Terms & ConditionsAccessibility statement