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 truly stumped. Does anyone have any ideas as to why this wouldn’t send to the correct category? I’m posting it as a FORM data (and not JSON, like Postman/tutorial says to do) No special headers - it’s pretty vanilla I copy+pasted “category” to ensure I didn’t typo it (shown in screenshot). It IS an number, right? I’m about to try it as text UPDATE: It IS an number, right? I’m about to try it as text Error 422 when I try it as string. It is definitely a number. UPDATE 2: Wait a sec… I’m still getting 422 errors even when account is admin? I guess this is for a new post

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 string.

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

[image] riking: supporting the id was an accident If it was an accident - that sounds a little cray-cray… [image]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 ID numbers.

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

DeanMarkTaylor (Dean Taylor) September 18, 2017, 8:01pm 4

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

Topic		Replies	Views
API POST to /posts.json inconsistent between users Bug	3	805	May 29, 2019
Posting to sub category not working for me Product Support	2	1273	June 2, 2017
Posting a new topic via API Development rest-api	7	4037	January 29, 2025
Create topic using Discourse API Development rest-api	3	1142	November 3, 2022
Using the Discourse API ruby gem to post a topic as a specific user Development rest-api	9	1413	October 3, 2018

Discourse always posts in general using API

Related topics