Overview
Supply the target post type (text or picture) along with an optional tone selection and an emoji toggle. The response returns an array containing generated comment strings matching the requested tone, which defaults to positive. The Free tier generates one comment per request, while paid plans can specify a count of up to 10.
Live Test Comment Generator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/commentgenerator?mode=text&tone=positive&count=5&emojis=true" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/commentgenerator?mode=text&tone=positive&count=5&emojis=true', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/commentgenerator?mode=text&tone=positive&count=5&emojis=true",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/commentgenerator?mode=text&tone=positive&count=5&emojis=true", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
modeRequired | string | The mode of comment generationtextpicture |
toneOptional | string | The tone of the commentspositivenegativeneutraldefault positive |
countOptionalPremium | integer | The number of comments to generate (max 10) default 1 · range 1–10 |
emojisOptional | boolean | Whether to include emojis in the comments default true |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"count": 5,
"mode": "text",
"tone": "positive",
"comments": [
"You're so right! is a game-changer Wow! 😍",
"Inspiring stuff gives me all the feels Wow! ✨",
"Thanks for sharing this gives me all the feels Perfect! 💯",
"Exactly my thoughts is on fire Wow beyond! 🌟",
"Great outlook in everything here, very bright! slays! For sure! 😊"
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 5 | Number of comments generated based on request |
mode | string | "text" | Comment generation mode used for comments |
tone | string | "positive" | Tone applied to all generated comments |
comments | array | [You're so right! is a game-changer Wow! 😍, ...] | Array of AI-generated social media comments |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Social Feed Automation
- Social media management apps generate quick draft replies in positive or neutral tones to speed up community manager workflows across image feeds.
- Synthetic Dataset Creation
- Machine learning teams produce labeled positive and negative social comments to train and test text sentiment classification algorithms.
- Forum Prototype Seeding
- When staging new social applications, developers populate mock feed discussions with sample image-post comments instead of manually writing placeholder copy.
- Moderation Bot Benchmarking
- Evaluate automated content filters by testing incoming negative comment responses against keyword rules and toxicity thresholds before deploying to production.
Other ways to use Comment Generator
Set up Comment Generator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Generation: