Why doesn't allow create secret with your own provided api key?

🤗Datasets
1

Why suddenly today I cannot add HF API key in the secret?

1 Like
2

I’ve seen this happen a couple times and it’s usually one of these:

  1. Temporary HF UI/backend hiccup
  • Secrets occasionally fails for a few hours when something is being rolled out. Easiest test: try again in 30 mins + check in another browser.
  1. Mobile/browser paste issues

  • On iOS/Safari the Secrets field can silently fail if the token has a trailing space/newline.

  • Paste into Notes first, re-copy (no newline), then paste again.

  • Or try desktop / private window.

  1. Secret name rules
  • Keep the secret name simple: HF_TOKEN (letters/numbers/underscore). No spaces/special chars.
  1. Permission / org restriction

  • If the Space is under an org, you might not have rights to add secrets (or org policies can block it).

  • Also check you’re in the right place: Space → Settings → Secrets (not model/dataset).

  1. Token issues
  • If the token was revoked/expired or missing scope, creating a fresh token often fixes it.

If you can share what you see when you click “Create secret” (error text / screenshot) + whether it’s a personal Space or org Space, I can tell you which of the above it is.
Hope this helps. Liam

1 Like