Lemmy Support @lemmy.ml Kristof Zerbe @programming.dev 2 wk. ago

Is it a bug that the response of .../api/v3/comment/list?post_id is always empty?

I try to get comment data for my posts via API from my Lemmy instance, but whatever I try on using the GetComments endpoint it delivers an empty array.

For example ... GET https://programming.dev/api/v3/comment/list?post_id=20878811 leads to:

{
  "comments": []
}

I want to ask here, before creating an issue. Has someone a hint?

4 comments

~~In 0.19.5, they removed the deprecated post_id tag, and replaced it with the post_ids array. If you ran that against an instance still running 0.19.4, it should work.~~

This is for posts, not comments, and doesn't affect the comment API.
- Thank you for the tip ... but whatever I try with the parameter post_ids in curl, my instance running 0.19.5 does not recognize the parameter and I receive a list with the latest comments over all posts ... !?
  
  Yeah, you're right. I didn't read enough of the docs. The new field is only for posts, not for comments. It looks like post_id should still be valid.

Oddly, the endpoint on lemm.el and lemmy.ml return comments:

> curl 'https://lemm.ee/api/v3/comment/list?post_id=45734814' | jq '.comments.[] | .comment.content[:50]'
"Yeah, you're right. I didn't read enough of the do"
"Thank you for the tip ... but whatever I try with "
"~~In 0.19.5, they removed the deprecated `post_id`"

> curl 'https://lemmy.ml/api/v3/comment/list?post_id=21766749' | jq '.comments.[] | .comment.content[:50]'
"Yeah, you're right. I didn't read enough of the do"
"Thank you for the tip ... but whatever I try with "
"~~In 0.19.5, they removed the deprecated `post_id`"

I think it would be better to ask the admin of the instance before creating the issue.