Générer/Regénérer api_key pour une API utilisateur ne fonctionne pas

Dev
1

J’essaie d’obtenir une clé API pour un utilisateur, mais je reçois une erreur 404.

Mes autres API fonctionnent correctement, donc ce n’est pas un problème d’en-tête. J’ai également vérifié la configuration du backend : aucun problème.

1 « J'aime »
2

The endpoint to create a new API key has changed - we’re working on updating the documentation ASAP. You can now create a new API key like this:

curl -X POST http://localhost:3000/admin/api/keys \
  -H "Content-Type: multipart/form-data;" \
  -H "Api-Key: $api_key" \
  -H "Api-Username: system" \
  -F "key[description]=testing" \
  -F "key[username]=bobby"

I would be interested to know why you are creating new API keys… using an API key. It seems a little circular, and I wonder if we can come up with a better solution for your problem?

7 « J'aime »
3

I have created a new user via API. (with admin API and KEY)
now I need to post a post or topic for this user.

But seems no API for me to do that… So I think maybe I should create a API for this user, then I switch my header with this new API… then I can make a post or topic on behalf of this new user…

1 « J'aime »
4

Rather than creating a key for each user, you can use an “all users” key, then change the Api-Username header on the request. There is an example at the top of https://docs.discourse.org/

3 « J'aime »
5

great man! thanks. that works perfectly !

1 « J'aime »
6

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