Twitter / X

Connect your Twitter/X account to schedule and publish tweets through Cue.

Overview

Twitter (also known as X) is a social media platform where you can post short messages called tweets. Cue integrates with the Twitter API v2 to publish content on your behalf.

Authentication

Twitter uses OAuth 2.0 for secure authentication. You don't need to create API credentials - Cue handles this for you.

Connecting Your Account

Go to Profiles in your Cue dashboard
Click Connect Account on a profile
Select Twitter / X
You'll be redirected to Twitter to authorize access
Sign in and grant Cue permission to post on your behalf
You'll be redirected back to Cue automatically

Your credentials are never shared with Cue.

Permissions

Cue requests the following permissions:

tweet.read - Read your tweets
tweet.write - Post tweets on your behalf
users.read - Read your profile information
offline.access - Maintain access when you're not using Cue

Disconnecting

To disconnect your Twitter account, go to your profile and click Disconnect next to the Twitter connection. This revokes Cue's access to your account.

Content Limits

Twitter enforces the following limits on tweets:

Limit	Value
Characters	280
Images	Up to 4 per tweet
Video length	2 minutes 20 seconds
GIF	1 per tweet
File size	5 MB (images), 512 MB (videos)

Cue automatically validates your content length before publishing to prevent errors.

Publishing a Tweet

curl -X POST https://api.oncue.so/v1/posts \
  -H "Authorization: Bearer cue_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": "prf_abc123",
    "platforms": {
      "sac_twitter1": {
        "items": [{ "content": "Hello from Cue!" }]
      }
    },
    "publishNow": true
  }'

const response = await fetch("https://api.oncue.so/v1/posts", {
  method: "POST",
  headers: {
    Authorization: "Bearer cue_sk_your_key_here",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    profileId: "prf_abc123",
    platforms: {
      sac_twitter1: {
        items: [{ content: "Hello from Cue!" }]
      }
    },
    publishNow: true,
  }),
});

Schedule for Later

curl -X POST https://api.oncue.so/v1/posts \
  -H "Authorization: Bearer cue_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": "prf_abc123",
    "platforms": {
      "sac_twitter1": {
        "items": [{ "content": "Scheduled tweet content" }]
      }
    },
    "scheduledAt": "2024-01-20T09:00:00-05:00"
  }'

const response = await fetch("https://api.oncue.so/v1/posts", {
  method: "POST",
  headers: {
    Authorization: "Bearer cue_sk_your_key_here",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    profileId: "prf_abc123",
    platforms: {
      sac_twitter1: {
        items: [{ content: "Scheduled tweet content" }]
      }
    },
    scheduledAt: "2024-01-20T09:00:00-05:00",
  }),
});

Creating Threads

Create multi-post threads by including multiple items in the items array. Each item becomes a connected tweet in the thread.

Threads require a Growth plan or above.

curl -X POST https://api.oncue.so/v1/posts \
  -H "Authorization: Bearer cue_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": "prf_abc123",
    "platforms": {
      "sac_twitter1": {
        "items": [
          { "content": "1/ Here'\''s a thread about building in public..." },
          { "content": "2/ First, we identified the problem we wanted to solve..." },
          { "content": "3/ Then we built a prototype and got early feedback..." },
          { "content": "4/ The results? 10x improvement in our workflow!" }
        ]
      }
    },
    "publishNow": true
  }'

const response = await fetch("https://api.oncue.so/v1/posts", {
  method: "POST",
  headers: {
    Authorization: "Bearer cue_sk_your_key_here",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    profileId: "prf_abc123",
    platforms: {
      sac_twitter1: {
        items: [
          { content: "1/ Here's a thread about building in public..." },
          { content: "2/ First, we identified the problem we wanted to solve..." },
          { content: "3/ Then we built a prototype and got early feedback..." },
          { content: "4/ The results? 10x improvement in our workflow!" }
        ]
      }
    },
    publishNow: true,
  }),
});

Each tweet in a thread must respect the 280 character limit.

Response

{
  "data": {
    "id": "pst_xyz789",
    "profileId": "prf_abc123",
    "content": "Hello from Cue!",
    "status": "queued",
    "scheduledAt": null,
    "createdAt": "2024-01-15T10:00:00Z",
    "updatedAt": "2024-01-15T10:00:00Z"
  },
  "message": "Post queued for publishing to 1 platform(s)"
}

Error Handling

Twitter API errors are translated into user-friendly messages:

Error Code	Meaning	Solution
`401`	Authentication failed	Reconnect your Twitter account
`403`	Account suspended or restricted	Check your Twitter account status
`429`	Rate limit exceeded	Wait and retry later
`400`	Content exceeds 280 characters	Shorten your content