# Multiple Audience

**URL:** <https://community.auth0.com/t/multiple-audience/87123>\
**Category:** Get Help\
**Tags:** python, api, auth0\
**Created:** [July 18, 2022, 12:19pm UTC](https://community.auth0.com/t/multiple-audience/87123 "2022-07-18T12:19:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [July 18, 2022, 11:48pm UTC](https://community.auth0.com/t/multiple-audience/87123/4 "2022-07-18T23:48:02Z")

</div>

Hello @authneumoney!

How exactly are you logging users in? Are you able to confirm that the access tokens granted don’t already contain the `/userinfo` audience as outlined below?

> [@Access token has two audiences?](https://community.auth0.com/t/access-token-has-two-audiences/71041/3):
>
> Hey @woeterman94 , You cannot remove the /userinfo audience. It is included by default for all issued Access Tokens. If you specify an audience of your custom API identifier and a scope of openid, then the resulting access token’s aud claim will be an array rather than a string, and the access token will be valid for both your custom API and for the /userinfo endpoint. Other than in the use case of a single custom API as well as Auth0’s /userinfo endpoint, your access tokens will be unable to …

Let us know!

---

_[View the full topic](https://community.auth0.com/t/multiple-audience/87123)._
