Whenever I post via the API, I tested it in Postman and it sends the right things to the right category. However, when I more or less copy+paste the same thing with an http POST (via JavaScript), I get everything right…EXCEPT the category (which I thought was the easiest part): [image] I’m just …

Ahhhh apparently error 422 is rate-limiting. The category “number” IS actually “text” (a string). Making bot account admin seemed to do the trick for the limiting (… but why do I have to make it an ADMIN to edit rate limiting? Seems a bit of a dramatic upgrade for such) and “15” as the category as a …

I believe the browser client submits the category as its name; supporting the id was an accident. See also: [imagem] 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 us…

[imagem] riking: supporting the id was an accident If it was an accident - that sounds a little cray-cray… [imagem] Posting to sub category not working for me It’s best to use the category ID integer value as indicated by the docs here: Discourse API Docs … I would stick with integer c…

Just wanted to clarify that when creating a topic in a category via the API, you specify the category by id now, not by name. [image]

Discourse always posts in general using API

Product Support

blake (Blake Erickson) 5 Outubro , 2019 21:53 6

Só queria esclarecer que, ao criar um tópico em uma categoria via API, você agora especifica a categoria pelo ID, não pelo nome.

Tópico		Respostas	Vistas
API POST to /posts.json inconsistent between users Bug	3	804	29 Maio , 2019
Posting to sub category not working for me Product Support	2	1267	2 Junho , 2017
Posting a new topic via API Development rest-api	7	4029	29 Janeiro , 2025
Create topic using Discourse API Development rest-api	3	1133	3 Novembro , 2022
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1399	3 Outubro , 2018

Discourse always posts in general using API

Related topics