Skip to content

X Settings

OpenQuok public API provider settings for X — reply audience, community, disclosures, thread finisher, follow-up replies, and cross-account reposts.

3 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start for $0

Quick reference

PropertyValue
Identifierx
ConnectGET /api/v1/public/social/x
Setup guideX
Character cap280 (standard) or 4,000 (verified) — weighted counting for links and mentions
Main-post mediaText-only OK; up to 4 images or one video (≤140 s); never mixed

Settings on create post

Nest X-specific keys under the x bucket in providerSettingsByIntegrationId[<integration-id>]. Flat API keys merge at publish time for compose settings.

Flat CLI / API keyNested composer bucketPurpose
who_can_reply_postx.whoCanReplyPostReply audience
communityx.communityUrlPost into an X community (URL or id)
made_with_aix.madeWithAiMade with AI disclosure
paid_partnershipx.paidPartnershipPaid partnership disclosure
x.repliesScheduled follow-up replies
x.enabled / x.messageThread finisher
x.crossAccountPlugsCross-account reposts
{
  "providerSettingsByIntegrationId": {
    "<x-integration-id>": {
      "who_can_reply_post": "following",
      "x": {
        "replies": [
          { "message": "2/2 — payoff", "delaySeconds": 90 }
        ],
        "enabled": true,
        "message": "Thanks for reading!",
        "crossAccountPlugs": [
          {
            "plugName": "x-repost-post-users",
            "enabled": true,
            "delayMs": 0,
            "integrationIds": ["<other-x-integration-id>"],
            "fields": {}
          }
        ]
      }
    }
  }
}

Field reference

FieldTypeRequiredNotes
who_can_reply_post / x.whoCanReplyPoststringNofollowing, mentionedUsers, subscribers, or verified
community / x.communityUrlstringNoCommunity URL or id resolved at publish
made_with_ai / x.madeWithAibooleanNoAI-generated content label
paid_partnership / x.paidPartnershipbooleanNoPaid partnership label
x.repliesarrayNoQuote-less follow-up tweets
x.replies[].messagestringYes (per row)Reply text (weighted length)
x.replies[].delaySecondsnumberYes (per row)Delay after previous part
x.replies[].mediaarrayNoUp to 4 images or one video per reply
x.enabledbooleanNoThread finisher
x.messagestringWhen finisher enabledClosing reply text
x.crossAccountPlugsarrayNoReposts from other X channels

Follow-up comments

Same-account quote-less replies use x.replies. Optional media per row follows the same upload rules as the main post (up to four images or one video).

Cross-account plugs

Plug idAction
x-repost-post-usersRepost from other X channels in the workspace (no fields)

Configure on the publishing channel’s x.crossAccountPlugs array. See Cross-account plugs.

Complete example

Post with reply audience and a two-part thread:

curl -X POST https://api.openquok.com/api/v1/public/posts 
  -H "Authorization: Bearer opo_your_programmatic_token" 
  -H "Content-Type: application/json" 
  -d '{
    "body": "1/2 — setup",
    "scheduledAt": "2026-05-15T10:00:00.000Z",
    "status": "scheduled",
    "integrationIds": ["<x-integration-id>"],
    "isGlobal": true,
    "providerSettingsByIntegrationId": {
      "<x-integration-id>": {
        "x": {
          "whoCanReplyPost": "following",
          "replies": [
            { "message": "2/2 — payoff", "delaySeconds": 90 }
          ]
        }
      }
    }
  }'
Search documentation
Find a docs page
Discord Support