Skip to main content
Hivra connects to X (formerly Twitter) through X’s official authorization flow. Once your account is linked, you can include X as a destination in the Hivra Composer. Each post consists of tweet text drawn from your caption and the video you uploaded — X does not offer per-video privacy levels in the same way as YouTube or TikTok, so posts are public by default on your timeline.

​
Connect your X account

1

Open Integrations

In Hivra, go to Dashboard → Integrations and find the X tile.
2

Start the redirect

Click Connect to start the authorization flow.
3

Authorize in X

You are redirected to X’s authorization page. Accept all requested permissions — these cover posting tweets with media on your behalf. Declining any scope prevents the connection from completing.
4

Verify the connection card

After the redirect returns you to Hivra, your X handle and profile picture appear on the integration card. The health chip reads Healthy once the monitoring job confirms the token is valid.
X publishes posts to your public timeline. There is no API-level option to post privately or restrict who sees a post beyond the reply settings described below.
X is the one platform where Hivra pays per API call, so your subscription includes a shared monthly budget for X usage. If that budget is used up for the month, connecting (or reconnecting) an X account is blocked until it resets — see Monthly X API budget below.

​
X publish settings

When you add X as a destination in the Composer, a settings panel appears with the following options.

​
Tweet text

The Tweet text field is populated from the Composer’s shared caption by default. X displays this text alongside your video on the timeline. Keep in mind X’s character limit when writing your caption — if the shared caption exceeds the limit, use the per-platform caption override to write a shorter version specifically for X.

​
Media attachment

The video you uploaded in the Composer is automatically attached to the post as the media. Hivra uploads the video file to X’s media endpoint before creating the tweet. No additional configuration is needed for the media attachment.

​
Per-platform caption override

To write a different tweet text specifically for X, click the X tile in the Customize Caption Per Platform section and enter your X-specific text. This is useful when your shared caption is too long for X’s character limit or when you want platform-specific copy, hashtags, or mentions on X.
Hashtags and @mentions in your X caption are hyperlinked automatically. Use the per-platform override to include X-specific hashtags that are not relevant to your other destinations.

​
Monthly X API budget

X is the only connected platform where X itself charges Hivra for every API call — reading posts, checking profiles, publishing, replying, and liking all have a cost. To keep plans affordable, every paid Hivra subscription includes a monthly budget for X API usage, shared across all workspaces owned by that subscription.
The X budget is shared by subscription, not per workspace — if you have several workspaces under the same billing owner, they all draw from the same monthly X budget. The Free plan has no X budget, so X cannot be connected on Free.
The budget resets at the start of each calendar month (UTC).

​
What happens as usage climbs

If your subscription hits the 130% limit and you try to add X as a destination in the Composer, a X paused for this month warning appears, X is automatically deselected, and your other selected platforms are not affected. The warning tells you the date the budget resets.

​
Checking your usage

On the Creator and Business plans, open Settings → Plan & billing to see an X API usage card showing how much of the monthly budget you’ve used so far, your current level, and the reset date. You can also choose how you’re notified about X usage — at 80%, 100%, and 130% — from Settings → Notifications, under X usage.

​
Reconnect your X account

If the X integration card in the dashboard overview shows Attention, your X token has expired or been revoked.
1

Open Integrations

Go to Dashboard → Integrations and locate the X card.
2

Click Reconnect

Click Reconnect on the card to restart the OAuth flow.
3

Re-authorize in X

Accept all permissions on X’s authorization page to issue a fresh token.
4

Confirm the health chip

Wait for the monitoring job to run. The chip should return to Healthy after the check runs.
Changing your X account password or revoking app access from X’s Settings → Security and account access → Apps and sessions will invalidate your Hivra token immediately. Reconnect from the Integrations page after any such change.