Twitter Comment without Images API
Creates a new text-only Twitter comment on an existing tweet. This endpoint is perfect for quick responses, discussions, and engagement that relies on compelling written content.
Endpoint Details
POST https://portfolio.tigest.club/api/v1/dashboard/post/webhook
Content-Type: multipart/form-data
Request Parameters
Parameter | Type | Required | Description | Valid Values | Example |
---|---|---|---|---|---|
channel | string | Yes | Target platform (always Twitter) | "Twitter" | ”Twitter” |
post_type | string | Yes | Type of content being posted | "comment" | ”comment” |
content | string | Yes | Text content of the comment | Up to 280 characters | ”gm gm” |
calendar_uuid | string | Yes | Unique identifier for your content calendar | Valid UUID format | ”69a1bf45-c48e-46cf-bd53-f47f3efa9763” |
scheduled_at | string | Yes | Publication date and time in ISO 8601 format | Future datetime in UTC | ”2025-05-30T21:30:00Z” |
status | string | Yes | Post publication status | "draft" , "published" , "scheduled" | ”draft” |
tweet_id | string | Yes | ID of the tweet being commented on | Valid Twitter tweet ID | ”1926945210002493637” |
Parameter Details
Content Guidelines:
- Character Limit: Each comment must be 280 characters or less
- Text Optimization: Make every character count for maximum impact
- Readability: Use clear, concise language for easy consumption
- Engagement: Encourage further discussion when appropriate
- Context: Ensure comment is relevant to the original tweet
Example Requests
Simple Response Comment
curl --location 'https://portfolio.tigest.club/api/v1/dashboard/post/webhook' \
--header 'X-API-KEY: your_api_key_here' \
--form 'content="gm gm"' \
--form 'channel="Twitter"' \
--form 'post_type="comment"' \
--form 'scheduled_at="2025-05-30T21:30:00Z"' \
--form 'status="draft"' \
--form 'calendar_uuid="69a1bf45-c48e-46cf-bd53-f47f3efa9763"' \
--form 'tweet_id="1926945210002493637"'
Detailed Response Comment
curl --location 'https://portfolio.tigest.club/api/v1/dashboard/post/webhook' \
--header 'X-API-KEY: your_api_key_here' \
--form 'content="Thanks for sharing! Here'\''s my perspective on this topic:\n\n1. First point\n2. Second point\n3. Third point\n\nWhat do you think about these points?"' \
--form 'channel="Twitter"' \
--form 'post_type="comment"' \
--form 'scheduled_at="2025-05-30T21:30:00Z"' \
--form 'status="draft"' \
--form 'calendar_uuid="69a1bf45-c48e-46cf-bd53-f47f3efa9763"' \
--form 'tweet_id="1926945210002493637"'
Response Format
Successful Response
Status Code: 200 OK
{
"data": {
"id": 1074029,
"uuid": "b9fc4bf0-12c6-4190-893c-58d814e2dae1",
"calendar_uuid": "69a1bf45-c48e-46cf-bd53-f47f3efa9763",
"calendar_user_uuid": "cb3c071c-319a-4dfb-ab0c-538339d18325",
"content": "gm gm",
"channel": "Twitter",
"images": [],
"status": "draft",
"scheduled_at": "2025-05-30T21:30:00Z",
"created_at": "2025-05-29T15:47:43.757008982Z",
"is_active": true,
"updated_at": "2025-05-29T15:47:43.757008982Z",
"post_type": "comment",
"post_content": {
"text": "gm gm",
"images": [],
"tweet_id": "1926945210002493637"
},
"metadata": {},
"campaign_uuid": null,
"analytics": {}
},
"success": true
}
Response Fields Explained
Field | Type | Description |
---|---|---|
id | integer | Unique numeric identifier for the comment |
uuid | string | Unique string identifier (use for API references) |
calendar_uuid | string | Links the comment to your content calendar |
calendar_user_uuid | string | Identifies the calendar owner |
content | string | The text content of the comment |
channel | string | Always “Twitter” for this endpoint |
images | array | Empty array (no images in text-only comments) |
status | string | Current comment status (draft/scheduled/published) |
scheduled_at | string | Scheduled publication time in UTC |
created_at | string | Comment creation timestamp |
is_active | boolean | Whether the comment is active in the system |
updated_at | string | Last modification timestamp |
post_type | string | Always “comment” for this endpoint |
post_content | object | Contains the complete comment structure |
metadata | object | Additional metadata about the comment |
campaign_uuid | string | Associated campaign identifier (if any) |
analytics | object | Comment performance data (populated after publication) |
Error Handling
Comment-Specific Errors
Invalid Tweet ID (Code: 4001)
{
"errors": {
"code": 4001,
"message": "Invalid tweet ID. The tweet does not exist or is not accessible."
},
"success": false
}
Solution: Ensure the tweet ID is valid and the tweet is accessible.
Character Limit Exceeded (Code: 4009)
{
"errors": {
"code": 4009,
"message": "Comment exceeds 280 character limit."
},
"success": false
}
Solution: Ensure your comment text is 280 characters or less.
Missing Content (Code: 4011)
{
"errors": {
"code": 4011,
"message": "Comment content is required."
},
"success": false
}
Solution: Provide text content for your comment.
Invalid Status (Code: 4012)
{
"errors": {
"code": 4012,
"message": "Invalid status value. Must be one of: draft, published, scheduled."
},
"success": false
}
Solution: Use a valid status value: “draft”, “published”, or “scheduled”.
Last updated: May 29, 2025