<commit_before>---
description: Describes what changed in the flow for generating Auth0 Management APIv2 tokens and why.
section: apis
crews: crew-2
toc: true
---

# Changes in Auth0 Management APIv2 Tokens

Recently we changed the process to get a Management APIv2 Token. This article explains what changed, why this was done and how you can work around it (not recommended).

## What changed and why

### The User Experience

Until recently you could generate a Management APIv2 Token directly from the Management API explorer. You selected the scopes, according to the endpoint you wanted to invoke, and got a token from that same page.

That way was very easy but it was also __very insecure__. So we changed it.

The new way uses the [OAuth 2.0 Client Credentials grant](/api-auth/grant/client-credentials).

You can get a new token either [using the dashboard](/api/management/v2/tokens#get-a-token-manually) (if you use the API sporadically) or [by configuring a server process](/api/management/v2/tokens#automate-the-process) (if you need a token frequently) that will get a new token every 24 hours.

::: note
For details on how to follow this new process refer to <a href="/api/management/v2/tokens">The Auth0 Management APIv2 Token</a>
:::<commit_msg>Update outdated term<commit_after>---
description: Describes what changed in the flow for generating Auth0 Management APIv2 tokens and why.
section: apis
crews: crew-2
toc: true
---
# Changes in Auth0 Management APIv2 Tokens

Some time ago we changed the process to get a Management APIv2 Token. This article explains what changed, why this was done and how you can work around it (not recommended).

## What changed and why

### The User Experience

Until recently you could generate a Management APIv2 Token directly from the Management API explorer. You selected the scopes, according to the endpoint you wanted to invoke, and got a token from that same page.

That way was very easy but it was also __very insecure__. So we changed it.

The new way uses the [OAuth 2.0 Client Credentials grant](/api-auth/grant/client-credentials).

You can get a new token either [using the dashboard](/api/management/v2/tokens#get-a-token-manually) (if you use the API sporadically) or [by configuring a server process](/api/management/v2/tokens#automate-the-process) (if you need a token frequently) that will get a new token every 24 hours.

::: note
For details on how to follow this new process refer to [The Auth0 Management APIv2 Token](/api/management/v2/tokens).
:::
{'fraction_non_alphanumeric': 0.06930693069306931, 'fraction_numerical': 0.012673267326732674, 'mean_word_length': 4.38592750533049, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1203026', 'n_tokens_mistral': 698, 'n_tokens_neox': 675, 'n_words': 361}