# Auth Token via Postman has no payload

**URL:** <https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170>\
**Category:** Get Help\
**Tags:** apis, application\
**Created:** [September 26, 2023, 2:15pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170 "2023-09-26T14:15:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![baynezy](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/baynezy/32/49885_2.png) [@baynezy](https://community.auth0.com/u/baynezy)\
**Post date:** [September 26, 2023, 2:15pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/1 "2023-09-26T14:15:28Z")

</div>

![image](https://global.discourse-cdn.com/auth0/original/3X/0/1/01f65708dc8cfa27b94b153670a244d1fc7fd22f.png)

I have configured postman as above. However, when I do this I get an access token with an empty payload.

```auto
eyJhbGciOiJkaXIiLCJlbmMiOiJBMjU2R0NNIiwiaXNzIjoiaHR0cHM6Ly9hZnRlcmxpZmUtZGV2LnVrLmF1dGgwLmNvbS8ifQ..ANVgXBZP8dlASE_S.rKuROKXZ7iViOaSMhZTNxQ3xhPvenHMLP25APdAs1nh3gutEV03nDYewPf6PWJwM8Za3KxhAgkkcrfuAVulkLmoN19QuON200N_GXATEeBdAagD2lknrsyDcknWgDB94d97pLqG_Nw3iZYOBJZmA9QcJQ0wrKgqX6iiINa7BABSzpkpxtM_dWIrTfR4qj6eTQjyON4YZbHyW4vBTXxcu55-0rTDAX1nPGrgcqYc9PEUCkoJr3g78q8adY1HjMQLEsnzyfUrWNOs0sNc5pga9snk9laaK9izcYU7mOeSkj6Tcnl41dhM_i-PAdYf23KUQdmspxibIxfcH7qHGjo6gH3XkCGUzhks-ei4E-egZhhI909fNlaVklDb1Z32SKpPl0Wl-gdBsiwW8Gleatbdska916ODf9it_6P-EBcMNpjIT-R9JiQ15GbWB-BM.2d7vP2ItTX2pDxVYeFCzrg

```

This is the decoded version from [JWT.io](http://JWT.io)

 ![image](https://global.discourse-cdn.com/auth0/original/3X/2/7/270c4fea04b776e10218b6d682a430ffb5c5874a.png)

The access token when I authenticate as that user via Authorisation Code Flow with PKCE has a full payload and the header has different properties.

What am I doing wrong?

---

<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:** [September 26, 2023, 7:52pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/3 "2023-09-26T19:52:02Z")

</div>

Hey there @baynezy !

From the looks of it, you aren’t passing an audience in the request to `/token` and are thus receiving an [opaque access token](https://community.auth0.com/t/why-is-my-access-token-not-a-jwt-opaque-token/31028) - If you add in an audience param (API identifier) you should be good to go.

[https://auth0.com/docs/get-started/authentication-and-authorization-flow/call-your-api-using-resource-owner-password-flow#example-post-to-token-url](https://auth0.com/docs/get-started/authentication-and-authorization-flow/call-your-api-using-resource-owner-password-flow#example-post-to-token-url)

---

<div class="post-metadata">

**Author:** ![baynezy](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/baynezy/32/49885_2.png) [@baynezy](https://community.auth0.com/u/baynezy)\
**Post date:** [September 27, 2023, 9:29am UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/4 "2023-09-27T09:29:20Z")

</div>

Thanks @ty.frith  
I have updated the request to include `audience` as a query string parameter. As postman doesn’t seem to support that natively.

[This article](https://community.postman.com/t/missing-audience-in-oauth2-0-authentication/37817) seems to suggest this is the correct solution.

However, I am still getting an opaque token.

I have read the article that you posted and double-checked that I am doing as it suggests. I am so lost on what to do next. As nothing I tweek seems to work.

---

<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:** [September 29, 2023, 6:04pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/5 "2023-09-29T18:04:50Z")

</div>

Hey @baynezy sorry for the delayed response!

> [@baynezy](#):
>
> However, I am still getting an opaque token.
> 
> I have read the article that you posted and double-checked that I am doing as it suggests. I am so lost on what to do next. As nothing I tweek seems to work.

Hmmm that’s super odd 🤔 I just tested in Postman myself, adding the `audience` param in the “Token Request” section and it’s working as expected. Can you double check that the `audience` you are passing is the exact same as the API Identifier listed for the API you’ve registered in Auth0? Additionally, it might be worth trying to [cURL](https://auth0.com/docs/get-started/authentication-and-authorization-flow/call-your-api-using-resource-owner-password-flow#example-post-to-token-url) outside of Postman to see if that works.

---

<div class="post-metadata">

**Author:** ![baynezy](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/baynezy/32/49885_2.png) [@baynezy](https://community.auth0.com/u/baynezy)\
**Post date:** [October 2, 2023, 1:23pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/6 "2023-10-02T13:23:27Z")

</div>

@ty.frith firstly, please don’t apologise for the slow response. I really appreciate your help.

Secondly, adding the audience to the **Token Request** section as a Request body parameter did mean I got back a non-opaque token. However, my API won’t accept it as it says it has the wrong audience. I am going to create a new topic about that, and I will link to it here.

Thanks again.

---

<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:** [October 16, 2023, 1:24pm UTC](https://community.auth0.com/t/auth-token-via-postman-has-no-payload/117170/7 "2023-10-16T13:24:07Z")

</div>

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