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: [imagen] 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…

[imagen] riking: supporting the id was an accident If it was an accident - that sounds a little cray-cray… [imagen] 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 Octubre, 2019 21:53 6

Solo quería aclarar que al crear un tema en una categoría mediante la API, ahora se especifica la categoría por su ID, no por su nombre.

Tema		Respuestas	Vistas
API POST to /posts.json inconsistent between users Bug	3	801	29 Mayo 2019
Posting to sub category not working for me Product Support	2	1256	2 Junio 2017
Posting a new topic via API Development rest-api	7	4012	29 Enero 2025
Create topic using Discourse API Development rest-api	3	1126	3 Noviembre 2022
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1386	3 Octubre 2018

Discourse always posts in general using API

Temas relacionados