Publier un nouveau sujet via API

Dev
1

Bonjour,

Je n’arrive pas à faire fonctionner la publication et, malheureusement, je n’ai pas trouvé grand-chose ni dans la documentation de l’API ni sur le forum.

Quel type d’encodage ou de nettoyage (le cas échéant) dois-je appliquer aux chaînes de titre et de corps brut du message ? J’obtiens étrangement une erreur 404 lors de la publication sur /posts.json avec les champs {api_username, api_key, title, raw, created_at, archetype, skip_validations} en utilisant un en-tête form-data (j’essaie avec Python, mais Postman donne le même résultat). Avez-vous des pistes sur ce que je fais mal ?

2

Standard www-form encoding is all. Make sure you’re sending either (api_username, api_key) or (Cookie, X-CSRF-Token).

5 « J'aime »
3

But am I supposed to receive 404 in any case? I do include api_username and api _key in the form…

Update: if I send the same request under admin user / master api_key it goes through, but I get 404 if I submit under another user but still with master api_key, bug or my mistake?

4

Can you provide more info and maybe a code snippet of your posting attempt?

3 « J'aime »
5

Hello - I don’t want to create a new topic because I seem to be having the exact same issue; I’m using the latest discourse_api gem, and I have generated a master API key; I’m creating posts on behalf of existing users (fetching content they put elsewhere).

A normal call

c.create_topic category: category, title: new_title,
                   raw: new_content, api_username: username

Works on some users, and not on others; I get a {"status"=>404, "error"=>"Not Found"} response.

Only differences I can tell are:

  • The user for whom I can create is in staff (others aren’t)
  • The user for whom I can create has a user name identical to the name, and is lowercase (others don’t and aren’t)

Furthermore, if I go to the web interface, create the post, and transfer ownership, it works. So far I’m letting the automaton do its job with the ones that can be created, and give me the text to manually create the ones that can’t. But at over 1000 posts that won’t be created automatically, I despair a little :sweat_smile:

EDIT: verified name situation is not the issue… It may be related to the staff thing.

EDITEDIT: I worked around this by creating in a user’s name, then changing ownership to another user. The mere fact that this is possible on the same API key makes me lean towards the 404 behavior being a bug.

2 « J'aime »
6

Avez-vous trouvé la solution ?

7

Comment envoyer une image dans l’API de création de publication. Car dans la documentation, il n’y a pas de clé mentionnée pour l’image dans la requête API.
https://docs.discourse.org/#tag/Posts/operation/createTopicPostPM

{
  "title": "string",
  "raw": "string",
  "topic_id": 0,
  "category": 0,
  "target_recipients": "blake,sam",
  "target_usernames": "string",
  "archetype": "private_message",
  "created_at": "string",
  "reply_to_post_number": 0,
  "embed_url": "string",
  "external_id": "string"
}
1 « J'aime »
8

Vous devez utiliser le point de terminaison uploads : \u003chttps://docs.discourse.org/#tag/Uploads\u003e
Ensuite, utilisez la valeur short_url retournée pour l’insérer dans votre publication.

2 « J'aime »