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 category …

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

サポート

DeanMarkTaylor (Dean Taylor) 2017 年 9 月 18 日午後 8:01 4

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

トピック		返信	表示
API POST to /posts.json inconsistent between users Bug	4	758	2019 年 6 月 1 日
Posting to sub category not working for me Support	4	1185	2019 年 7 月 13 日
Posting a new topic via API Development rest-api	7	3829	2025 年 1 月 29 日
Create topic using Discourse API Development rest-api	3	1037	2022 年 11 月 3 日
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1282	2018 年 10 月 3 日

Discourse always posts in general using API

関連トピック