# Token authentification + Alive

**URL:** <https://community.n8n.io/t/token-authentification-alive/20017>\
**Category:** Questions\
**Tags:** external-api\
**Created:** [November 21, 2022, 8:20pm UTC](https://community.n8n.io/t/token-authentification-alive/20017 "2022-11-21T20:20:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [November 23, 2022, 3:11pm UTC](https://community.n8n.io/t/token-authentification-alive/20017/2 "2022-11-23T15:11:23Z")

</div>

Hi @Daradaal, the `/api/Authenticated/Alive` looks like a test request to make sure a token is valid. Is the first request (`/api/Authenticated`) used to renew the token? How often would you need to run it to get a fresh token?

My first thought would be to have one workflow simply renewing the token as often as needed and writing the current token somewhere other workflows can read it from (a database or perhaps just a file).

---

_[View the full topic](https://community.n8n.io/t/token-authentification-alive/20017)._
