V3.4.0. beta4 dev API Keys settings have been changed to English, which was originally displayed in Chinese,
After successfully adding API key, the key is not displayed. Where can I see the key
You can’t.
For security reasons it is displayed when you create it, then mostly hidden.
So be sure to copy it when you create it.
For now, delete this one and create a new one, remembering to copy it during the creation process.
(FYI this follows convention on most similar API key creation workflows on other platforms)
4 Likes
I Know, For security reasons it is displayed when you create it, then mostly hidden.
When I created it before, it would be displayed once and then hidden
Now, when it is created, it is hidden and not displayed
3 Likes
When you hit save, you should see this:
When the English text is changed or new texts are added someone has to translate them before you can see the Chinese translation. As long as nobody has added a translation for those strings on Crowdin you will see the English text. That’s why it can take some time until texts are available in different languages.
2 Likes
Using the lastest version of Discourse I also have the problem.
Maybe there is a problem with the redesign?
1 Like
oh … maybe this is a regression, I have alerted the team
thanks for reporting
8 Likes
I’m experiencing the same issue. Go through all the steps outlined, yet the key is not displayed after hitting save. Just goes back to the main API Key screen. It’s preventing me from moving ahead with some critical work.
3 Likes
FWIW the HTTP response does contain the API key so if you “inspect” in your browsers devtools, you can get the key.
4 Likes
I am also experiencing this issue.
FWIW the HTTP response does contain the API key so if you “inspect” in your browsers devtools, you can get the key.
That helped, thanks!
Thank you for reporting this, @qiancsf. 
The step where you can copy the key was accidentally lost as we were working on this page. It has been added back in this PR:
4 Likes