# Auth0js - checkSession call Limit

**URL:** <https://community.auth0.com/t/auth0js-checksession-call-limit/17264>\
**Category:** Get Help\
**Tags:** limits, checksession, auth0\
**Created:** [October 26, 2018, 1:06pm UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264 "2018-10-26T13:06:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![clementt](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@clementt](https://community.auth0.com/u/clementt)\
**Post date:** [October 26, 2018, 1:06pm UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264/1 "2018-10-26T13:06:56Z")

</div>

Hi,

We currently implementing Silent Authentication on our Web App (Single App - React).

The documentation is very clear about that. The right way seems to be using the method checkSession() for having a new valid access Token.

However, it also seems that there is a limit between two calls for this method, actually 15 minutes.

Does it means that :

- if the token life time is less than 15 minutes, can we block the access to the API for everyone ?
- if someone create a loop on this method can he block the access to the API for everyone ?

Thanks for answers !

---

<div class="post-metadata">

**Author:** ![kimcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/kimcodes/32/81052_2.png) [@kimcodes](https://community.auth0.com/u/kimcodes)\
**Post date:** [October 29, 2018, 4:49pm UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264/3 "2018-10-29T16:49:00Z")

</div>

👋 @clement I am not sure I understand your questions fully - are you looking to restrict how often you call the `checkSession` method?

---

<div class="post-metadata">

**Author:** ![clementt](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@clementt](https://community.auth0.com/u/clementt)\
**Post date:** [October 31, 2018, 1:08pm UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264/4 "2018-10-31T13:08:09Z")

</div>

Sorry if it was not clear 😅

Actually I want to know if there is a restriction of call with checkSession by default.

If yes, how many ?

---

<div class="post-metadata">

**Author:** ![kimcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/kimcodes/32/81052_2.png) [@kimcodes](https://community.auth0.com/u/kimcodes)\
**Post date:** [December 5, 2018, 10:30am UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264/5 "2018-12-05T10:30:58Z")

</div>

Hi @clementt it is no problem! I apologize for the delay on response, if we set the `SSO Cookie Timeout` to something like 1 minute. And we proceed with our application, we perform the authentication flow and establish a session, we perform a `checkSession` call the call will work. If we wait for the session to expire, for example around 2 minutes after (remember we set `SSO Cookie timeout` to 1 minute and we perform a `checkSession` call it will fail. But, if we set to call `checkSession` before the `SSO Cookie Timeout` then we can silently re-authenticate the user and they can continue to use the application.

---

<div class="post-metadata">

**Author:** ![jerdog](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jerdog/32/11231_2.png) [@jerdog](https://community.auth0.com/u/jerdog)\
**Post date:** [January 22, 2019, 12:00am UTC](https://community.auth0.com/t/auth0js-checksession-call-limit/17264/6 "2019-01-22T00:00:01Z")

</div>

This topic was automatically closed after 14 days. New replies are no longer allowed.
