# No payload in access token

**URL:** <https://community.auth0.com/t/no-payload-in-access-token/76936>\
**Category:** JWT.io\
**Tags:** jwt, auth0, login\
**Created:** [January 24, 2022, 11:33pm UTC](https://community.auth0.com/t/no-payload-in-access-token/76936 "2022-01-24T23:33:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joelheath29](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/joelheath29/32/34638_2.png) [@joelheath29](https://community.auth0.com/u/joelheath29)\
**Post date:** [January 24, 2022, 11:33pm UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/1 "2022-01-24T23:33:13Z")

</div>

Hello everyone!  
I’m trying to get JWT access tokens for users that log into my website, so I can use the JWT’s on my server to authenticate requests, however, all of the access tokens I am getting are not working. This is what I get:

 ![Screenshot 2022-01-23 at 23.15.47](https://global.discourse-cdn.com/auth0/original/3X/2/2/22c526673c64755a755807cb62bef34b4ae79274.png)

Does anyone know how to fix this?  
Thanks

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 25, 2022, 1:20am UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/3 "2022-01-25T01:20:44Z")

</div>

Hi @joelheath29,

Welcome to the Auth0 Community!

I understand you have issues decoded your access token.

First, could you please clarify if you have specified the `audience` parameter in your `/authorize` request?

And could you please share your complete `/authorize` and `/oauth/token` requests?

Thank you.

---

<div class="post-metadata">

**Author:** ![joelheath29](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/joelheath29/32/34638_2.png) [@joelheath29](https://community.auth0.com/u/joelheath29)\
**Post date:** [January 25, 2022, 4:04pm UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/4 "2022-01-25T16:04:44Z")

</div>

Hi @rueben.tiow,

Is it the request payload for /authorize and /oauth/token requests on the client side that you want me to send?

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 25, 2022, 4:26pm UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/5 "2022-01-25T16:26:27Z")

</div>

Hi @joelheath29,

> [@joelheath29](#):
>
> Is it the request payload for /authorize and /oauth/token requests on the client side that you want me to send?

Yes please. [Here](https://auth0.com/docs/get-started/authentication-and-authorization-flow/call-your-api-using-the-authorization-code-flow) is an example.

Thank you!

---

<div class="post-metadata">

**Author:** ![Keanu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/keanu/32/33313_2.png) [@Keanu](https://community.auth0.com/u/Keanu)\
**Post date:** [January 28, 2022, 9:27am UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/6 "2022-01-28T09:27:14Z")

</div>

That would do it. I am going to open a ticket to look at a 200 when the region does not point to the right region. That seems like a bug. Thanks and I hope this did not cause you too many problems[.](https://www.alaskasworld.review/)

---

<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:** [February 12, 2022, 9:27am UTC](https://community.auth0.com/t/no-payload-in-access-token/76936/7 "2022-02-12T09:27:28Z")

</div>

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