APIsCommentComment Without Image

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

ParameterTypeRequiredDescriptionValid ValuesExample
channelstringYesTarget platform (always Twitter)"Twitter"”Twitter”
post_typestringYesType of content being posted"comment"”comment”
contentstringYesText content of the commentUp to 280 characters”gm gm”
calendar_uuidstringYesUnique identifier for your content calendarValid UUID format”69a1bf45-c48e-46cf-bd53-f47f3efa9763”
scheduled_atstringYesPublication date and time in ISO 8601 formatFuture datetime in UTC”2025-05-30T21:30:00Z”
statusstringYesPost publication status"draft", "published", "scheduled"”draft”
tweet_idstringYesID of the tweet being commented onValid 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

FieldTypeDescription
idintegerUnique numeric identifier for the comment
uuidstringUnique string identifier (use for API references)
calendar_uuidstringLinks the comment to your content calendar
calendar_user_uuidstringIdentifies the calendar owner
contentstringThe text content of the comment
channelstringAlways “Twitter” for this endpoint
imagesarrayEmpty array (no images in text-only comments)
statusstringCurrent comment status (draft/scheduled/published)
scheduled_atstringScheduled publication time in UTC
created_atstringComment creation timestamp
is_activebooleanWhether the comment is active in the system
updated_atstringLast modification timestamp
post_typestringAlways “comment” for this endpoint
post_contentobjectContains the complete comment structure
metadataobjectAdditional metadata about the comment
campaign_uuidstringAssociated campaign identifier (if any)
analyticsobjectComment 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