I’ve done a fair amount of work over the years with Discourse’s API and it’s always felt really inconsistent. I’m not trying to be critical, but your attitude seems pretty dismissive of something that is clearly inconsistent. I detailed in the first post that all requests that I reviewed returned one way, and after the upgrade to 1.5.1 the API started returning a different content-type in this one particular case. You can chalk this up as not a big deal, but APIs being consistent and reliable is important. If you want to continue to have software that people want use and integrate with you should care about the details.
citadelgrad
(Scott Nixon)
10
Related topics
| 글 | 댓글 | 조회수 | 활동 | |
|---|---|---|---|---|
| [API] In the Documentation: Wrong Key in the API Suspend | 3 | 673 | 11월 30, 2017 | |
| Suspend API Not Working | 11 | 1402 | 6월 22, 2018 | |
| 500 or 400 when updating the content of a post using the API | 4 | 1644 | 4월 24, 2019 | |
| Improve BAD CSRF error message when making API calls with content-type application/json | 4 | 4443 | 9월 14, 2020 | |
| API Error Message Format | 5 | 1736 | 11월 14, 2016 |