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: [이미지] 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…

[이미지] riking: supporting the id was an accident If it was an accident - that sounds a little cray-cray… [이미지] 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 categor…

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

Support

DeanMarkTaylor (Dean Taylor) 9월 18, 2017, 8:01오후 4

If it was an accident - that sounds a little cray-cray…

글		댓글	조회수
API POST to /posts.json inconsistent between users Bug	3	787	5월 29, 2019
Posting to sub category not working for me Support	2	1234	6월 2, 2017
Posting a new topic via API Development rest-api	7	3937	1월 29, 2025
Create topic using Discourse API Development rest-api	3	1094	11월 3, 2022
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1347	10월 3, 2018

Discourse always posts in general using API

Related topics