Hello, I cannot seem to make posting work and unfortunately couldn’t find much neither in api docs, nor on the forum - What type of encoding/cleaning (if any) do I have to do for the title and raw post body strings? I’m strangely getting 404 when posting on /posts.json with {api_username, api_key, title, raw, created_at, achetype, skip_validations} fields with form-data header (trying with python but postman gives the same). Any pointers to what am I doing wrong?

Standard www-form encoding is all. Make sure you’re sending either (api_username, api_key) or (Cookie, X-CSRF-Token). [image] Reverse engineer the Discourse API Integrations Discourse is backed by a complete JSON api. Anything you can do on the site you can also do using the JSON api. The API is documented at docs.discourse.org. You can also use the discourse_api Ruby gem as a client library. However, not every endpoint is documented. To determine how to do something with the JSON API here are some steps you can follow. Example: recategorize a topic. Go to a topic and start editing a category: [image] Open Chrome dev tools, switch to the Network tab, select …

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?

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

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.

How to send an image in the create post api. Because in docs in api request there is no key mention for image. 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" }

Posting a new topic via API

Development

Canapin (Coin-coin le Canapin) January 29, 2025, 11:11am 8

You must use the uploads endpoint: https://docs.discourse.org/#tag/Uploads
Then, use the returned short_url value to insert it in your post.

Topic		Replies	Views
Create topic using Discourse API Development rest-api	3	1141	November 3, 2022
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1412	October 3, 2018
Create topic with Discourse API Development	0	471	November 1, 2022
Posting new topic via the API not working Product Support	2	1280	September 27, 2017
Is there a way to post as an arbitrary user when creating a new post/topic using the Discourse API? Product Support	8	1293	May 11, 2017

Posting a new topic via API

Related topics