Title: JSON API &#8211; Comment Author Issue
Last modified: August 24, 2016

---

# JSON API – Comment Author Issue

 *  [aheadzen](https://wordpress.org/support/users/aheadzen/)
 * (@aheadzen)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/json-api-comment-author-issue/)
 * Hello,
 * Jetpack is a great plugin and we use it for its cool JSON API on a self-hosted
   WordPress setup.
 * I am facing a problem while retrieving comments for a particular post page, the
   returned author object is always same (admin in my case) but it should be really
   comment author as shown in documentation.
 * This is the API url that I am trying – [https://public-api.wordpress.com/rest/v1.1/sites/www.ask-oracle.com/posts/978/replies/?pretty=1](https://public-api.wordpress.com/rest/v1.1/sites/www.ask-oracle.com/posts/978/replies/?pretty=1)
   
   As you can see above, author object is always same and not really the comment
   author. It can verified from this webpage – [http://www.ask-oracle.com/sign-compatibility/aries-man-taurus-woman/](http://www.ask-oracle.com/sign-compatibility/aries-man-taurus-woman/)
 * However it is working as expected when I query any particular comment – [https://public-api.wordpress.com/rest/v1.1/sites/www.ask-oracle.com/comments/1296560/?pretty=1](https://public-api.wordpress.com/rest/v1.1/sites/www.ask-oracle.com/comments/1296560/?pretty=1)
 * I am not sure what I am doing wrong (or what might cause problem on my setup).
   It is working good on the url provided within documentation – [https://public-api.wordpress.com/rest/v1/sites/en.blog.wordpress.com/posts/7/replies/?pretty=1](https://public-api.wordpress.com/rest/v1/sites/en.blog.wordpress.com/posts/7/replies/?pretty=1)
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [aheadzen](https://wordpress.org/support/users/aheadzen/)
 * (@aheadzen)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/json-api-comment-author-issue/#post-6100050)
 * I tried to var_dump author on the get_author function in class WPCOM_JSON_API_Endpoint
   but then API started giving verification errors, so I am unable to pin point 
   what might cause such behaviour.
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [11 years, 1 month ago](https://wordpress.org/support/topic/json-api-comment-author-issue/#post-6100105)
 * Could you send us more details about your setup and the way you make your queries
   through this form?
    [https://developer.wordpress.com/contact/](https://developer.wordpress.com/contact/)
 * Thanks!
 *  Thread Starter [aheadzen](https://wordpress.org/support/users/aheadzen/)
 * (@aheadzen)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/json-api-comment-author-issue/#post-6100121)
 * Thanks for quick response. Sent on contact form!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘JSON API – Comment Author Issue’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [author](https://wordpress.org/support/topic-tag/author/)
 * [Comments](https://wordpress.org/support/topic-tag/comments/)
 * [json](https://wordpress.org/support/topic-tag/json/)
 * [self-hosted](https://wordpress.org/support/topic-tag/self-hosted/)

 * 3 replies
 * 2 participants
 * Last reply from: [aheadzen](https://wordpress.org/support/users/aheadzen/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/json-api-comment-author-issue/#post-6100121)
 * Status: not resolved