# Access token with custom API scopes through Implicit Flow?

**URL:** <https://community.auth0.com/t/access-token-with-custom-api-scopes-through-implicit-flow/200692>\
**Category:** Get Help\
**Tags:** oidc, protocols\
**Created:** [June 9, 2026, 3:00pm UTC](https://community.auth0.com/t/access-token-with-custom-api-scopes-through-implicit-flow/200692 "2026-06-09T15:00:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adelin](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/adelin/32/72177_2.png) [@Adelin](https://community.auth0.com/u/Adelin)\
**Post date:** [June 9, 2026, 3:00pm UTC](https://community.auth0.com/t/access-token-with-custom-api-scopes-through-implicit-flow/200692/1 "2026-06-09T15:00:34Z")

</div>

I am wondering whether it is possible to get an user access token with a custom scope for an API that is configured to allow all apps for User-Delegated Access.

I tried to just add the scope in the /authorize request, but it just gets dropped and I get an access token with an empty string as scope claim.

I tried with both response\_type=token and with response\_type=code with PKCE.  
I also tried changing the API’s User-delegated Access to per app authorization and manually granting the scope I’m looking for to that app (of course User Delegated access) with no success.

Can one get a user access token with a custom API scope? Under what conditions?

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [June 10, 2026, 12:12am UTC](https://community.auth0.com/t/access-token-with-custom-api-scopes-through-implicit-flow/200692/3 "2026-06-10T00:12:14Z")

</div>

Hi @Adelin

Welcome to the Auth0 Community!

I understand that you are trying to add custom scopes for a user access token via Implicit Flow.

Allow me to share some details as to why you could be seeing this behaviour:

- Missing the audience property: Not including the audience parameter in the `/authorize` request can lead to an opaque access token. If you do not specify your custom API’s identifier as the `audience` (either in your SDK config or directly in the query parameters), Auth0 will issue a “scopeless”, opaque, or standard OIDC token that only contains standard OIDC scopes like `openid profile email`

```auto
GET /authorize?
    response_type=token id_token
    &scope=openid email
    &client_id=123
    &state=af0ifjsldkj
    &nonce=jxdlsjfi0fa
    &redirect_uri=https://app.example.com
    &audience=https://api.example.com

```

- User could be missing the required permissions: Since scopes in user flows represent delegated user privileges, the user logging in _must actually possess_ the permission. As you mentioned User-Delegated Access, this can be achieved via user Roles → I can recommend reading our documentation on [Delegated Administration: Manage Users - Auth0 Docs](https://auth0.com/docs/customize/extensions/delegated-administration-extension/delegated-administration-manage-users)

Below are a series of docs and articles that focus on various aspects of your implementation which should provide useful information:

- [API Access Policies for Applications - Auth0 Docs](https://auth0.com/docs/get-started/apis/api-access-policies-for-applications);
- [Implicit Flow with OIDC](https://auth0.com/docs/authenticate/login/oidc-conformant-authentication/oidc-adoption-implicit-flow);
- [Request custom API access](https://auth0.com/docs/get-started/apis/scopes/sample-use-cases-scopes-and-claims#request-custom-api-access).

Let us know if this helped!

Best regards,  
Gerald

---

<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:** [June 29, 2026, 8:29pm UTC](https://community.auth0.com/t/access-token-with-custom-api-scopes-through-implicit-flow/200692/4 "2026-06-29T20:29:45Z")

</div>

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