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.

Samuel Aguilera

The WordPress REST API is a great resource, but if you don’t want to use it probably you will want to close this door to your WordPress.
Unlike other popular plugins that aims to disable the REST API but only return an error, processed by the REST API, when a request is received, by default, this plugin removes all filters and actions related to WordPress REST API, and returns a 404 error for requests sent to the REST API URL endpoints, effectively blocking any use of the REST API.
Optionally you can set the REST API setting in Settings -> General page to “Logged In Only” for a less drastical action, to keep REST API access enabled but require the user to be logged in to accept the requests.
If you’re happy with the plugin <a href="https://wordpress.org/plugins/sar-disable-rest-api/reviews/?filter=5" rel="ugc">please don’t forget to give it a good rating</a>, it will motivate me to keep sharing and improving this plugin (and others).
SUPPORT: If you have any support question, please <a href="https://github.com/samuelaguilera/sar-disable-rest-api/issues" rel="nofollow ugc">create an issue at the Github repository</a>.
<h4>Requirements</h4>
<ul>
<li>WordPress 4.7 or higher.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Disable WordPress core REST API for real by removing all filters and actions related to it and returning a 404 error for requests sent to REST API URL endpoints (e.g. https://example.com/wp-json/whatever ).</li>
<li>Option to require user to be logged in to use the REST API instead of completely disable it.</li>
</ul>
<h4>Usage</h4>
To disable the REST API completely simply install the plugin from the Plugins page and enable it.
If you don’t want to disable the REST API but require user to be logged in instead, go to Settings -> General page and set the REST API to option to “Logged In Only”, and click Save Changes.
You can change the option back to “Off” if you want to disable the REST API again.
To return to WordPress default, simply deactivate the plugin.

Disable REST API for Real

A simple way to disable WordPress REST API.



One click plugin

Really prevents the REST API from handling requests (default) or require user to be logged in.

REST API Comment vs Disable REST API for Real