Joaquim Domingos António

If you wish to ‘Create comments’ using REST API, without exposing Administrator credentials to the Front-End application, you are at the right place. Since WordPress 4.7, REST API was natively included in WordPress.
In order to ‘Create a comment’ , the authentication for a user with ‘Administrator’ role is required. While this is a deliberately done for security reasons, such implementation makes it very hard for Front-End applications to implement a simple ‘Post Comment’ or ‘Reply Comment’ function.
This plugin fulfils such requirement by extending the existing WordPress REST API endpoints.
Requirements:
Minimum PHP version: 7.0 
Minimum WordPress version: 5.5
Installation:
Download the plugin form wordpress marketplace install it like any other WordPress plugin. 
After the installation activate the plugin through the ‘Plugins’ menu in WordPress
Endpoint:
When this plugin is installed one new endpoint is added to the wp/v2 namespace.
 Endpoint 
 HTTP Verb 
 Permalinks
 */wp-json/wp/v2/comments/create 
 POST 
 enabled
 */?rest_route=/wp/v2/comments/create 
 POST 
 disabled
Usage:
<ol>
<li>Create a Comment</li>
</ol>
To create a comment using REST API, send a <code>POST</code> request to:
<blockquote>
<code>/wp-json/wp/v2/comments/create</code> – if permalinks is enabled on your wordpress website.
</blockquote>
Or
<blockquote>
<code>/?rest_route=/wp/v2/comments/create</code> if permalinks is not enabled on your wordpress website.
</blockquote>
With a JSON body, as shown bellow:
<pre><code>`Json
</code></pre>
{ 
 “post”: “Post ID”, 
 “author_name”: “Comment Author’s name”, 
 “author_email”: “Comment Author’s email”, 
 “content”: “Comment content” 
} 
 `
The content may also be send as an object:
<pre><code>`Json
</code></pre>
{ 
 “post”: “Post ID”, 
 “author_name”: “Comment Author’s name”, 
 “author_email”: “Comment Author’s email”, 
 “content”: { 
 “raw”:”Comment content” 
 } 
} 
 `
Set header to:
<pre><code>`
</code></pre>
content-type: application/json 
 ` 
If successful, you should receive a response with the data of the created comment:
<pre><code>`Json
</code></pre>
{ 
 “id”: “[comment id]”, 
 “status”: “[comment status]”, 
 “message”:”[server response message]” 
} 
 `
In response header the status code should be:
<pre><code>`Http
</code></pre>
HTTP 201 Created 
 `
<ol>
<li>Reply a comment</li>
</ol>
To reply a comment you just need to add the field parent for the parent comment to the JSON body
<pre><code>`Json
</code></pre>
{ 
 “post”: “Post ID”, 
 “author_name”: “Comment Author’s name”, 
 “author_email”: “Comment Author’s email”, 
 “content”: “Comment content”, 
 “parent”:”Comment parent ID” 
} 
 `
<blockquote>
Note: Ensure the parent is a comment id that belongs to the post informed in the field post. The comment parent post id must match the post id otherwise the following error will be shown:
</blockquote>
<pre><code>`Json
</code></pre>
{ 
 “code”: “rest_post_mismatch_parent_post_id”, 
 “message”: “Post ID and Parent post ID does not match”, 
 “data”: { 
 “status”: 400 
 } 
} 
 `
<h3>Contact</h3>
If there is any thing to say about the plugin fill free to <a href="mailto:sopport@appsdabanda.com" rel="nofollow ugc">contact us</a>.

REST API Comment

REST API Comment adds in the 'Comment creation' function to the Wordpress REST API.

Dave McHale

Tang Rufus

The most comprehensive plugin for controlling access to the WordPress REST API!
Works as a “set it and forget it” install. Just upload and activate, and the entire REST API will be inaccessible to your general site visitors.
But if you do need to grant access to some endpoints, you can do that too. Go to the Settings page and you can quickly whitelist individual endpoints (or entire branches of endpoints) in the REST API.
You can even do this on a per-user-role basis, so your unauthenticated users have one set of rules while WooCommerce customers have another while Subscribers and Editors and Admins all have their own. NOTE: Out of the box, all defined user roles will still be granted full access to the REST API until you choose to manage those settings.
For most versions of WordPress, this plugin will return an authentication error if a user is not allowed to access an endpoint. For legacy support, WordPress 4.4, 4.5, and 4.6 use the provided <code>rest_enabled</code> filter to disable the entire REST API.

Disable REST API

The plugin uses a is_user_logged_in() check to grant access to disabled REST API endpoints. I run a membership site for one year and just realized it now, that any logged in visitor STILL HAVE ACCESS to any disabled REST API endpoints.

This should be very explicit, and there should be a setting in the plugin settings page to set the minimum role for the user to have access to the disabled endpoints.

ANY logged-in visitor can view the disabled endpoints


Blocking the REST API entirely breaks plugins that require this functionality, so being able to selectively enable routes is perfect.



I recommend this plugin to everyone who uses Independent Analytics to secure their site while still enabling analytics to be recorded.


Excellent solution


The plugin does what it says on the tin, without being pretentious. Absolutely fantastic!


Fantastic

Disable the use of the REST API on your website to site users. Now with User Role support!

REST API Comment vs Disable REST API