# Unable to set non-default token expiry for Auth0 access\_token

**URL:** <https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740>\
**Category:** Get Help\
**Tags:** access-token\
**Created:** [January 9, 2023, 5:10am UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740 "2023-01-09T05:10:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gangas](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gangas/32/42416_2.png) [@gangas](https://community.auth0.com/u/gangas)\
**Post date:** [January 9, 2023, 5:10am UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740/1 "2023-01-09T05:10:19Z")

</div>

We want to set access\_token expiry with different value for each Auth0 client/application. We are passing audience parameter in /oauth/token API to create token. A default value of access\_token expiry is getting set for all applications. The default value seems to be coming from the Token-Expiration value defined in our API settings page under Auth0 Applications-\>API page.  
We don’t want the same default access\_token expiry for all applications but want different value for each application(client). How can we do this?

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [January 11, 2023, 1:47am UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740/3 "2023-01-11T01:47:46Z")

</div>

Hi there @gangas welcome to the community!

> [@gangas](#):
>
> A default value of access\_token expiry is getting set for all applications. The default value seems to be coming from the Token-Expiration value defined in our API settings page under Auth0 Applications-\>API page.

You’re correct here in that the at lifetime comes from the API settings in your Auth0 dashboard - One workaround may be to create separate APIs and therefore audiences per application in your dashboard. Although a bit more overhead, in the end they relate to the same resource server/API.

---

<div class="post-metadata">

**Author:** ![gangas](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gangas/32/42416_2.png) [@gangas](https://community.auth0.com/u/gangas)\
**Post date:** [January 11, 2023, 5:08am UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740/4 "2023-01-11T05:08:15Z")

</div>

Thanks for the confirmation and for suggesting a possible workaround.

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [January 11, 2023, 10:52pm UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740/5 "2023-01-11T22:52:01Z")

</div>

No problem, happy to help! 🚀

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 25, 2023, 10:52pm UTC](https://community.auth0.com/t/unable-to-set-non-default-token-expiry-for-auth0-access-token/97740/6 "2023-01-25T22:52:22Z")

</div>

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