Publishing to X/Twitter with the Twitter connector Publishing to X/Twitter with the Twitter connector
  1. Wildmoka
  2. Publish Destinations
  3. Social Destinations

Publishing to X/Twitter with the Twitter connector

Social Destinations

Wildmoka lets you connect a X/Twitter account as a publishing destination so you can push video clips and live streams directly from your Wildmoka workspace. 

 

1. Configure a X/Twitter account in Wildmoka

  1. In the Wildmoka main menu bar, go to Destinations, click the + button (Add destination) and select Twitter from the list of platform connectors.
  2. Click Select Wildmoka Twitter Application. You'll be redirected to X/Twitter's authorization page. You are redirected to the platform's own login/authorization page to sign in and authorize Wildmoka. Wildmoka never sees your password.
  3. Grant the requested permissions (read your profile, read and post content). After you approve, you're redirected back to Wildmoka and the account appears in your destinations list with its handle and avatar.

Things to know:

  • Wildmoka stores the access token issued for your account. If you change your account password, or revoke Wildmoka's access from the platform's own security settings (Connected apps), publishing will start failing and you'll need to re-authorize the destination in Wildmoka.
  • Whether Amplify/Studio fields actually appear depends on your X/Twitter account's own entitlements from the X/Twitter platform — this is granted on the platform side, not by Wildmoka.
     

2. Publish a video clip to X/Twitter

From the clip editor, the right-side Publish Panel is the UI operators interact with when selecting and configuring publish destinations. 

To publish a clip to X/Twitter, click on the + icon and select a X/Twitter account from your destinations.

Then scroll down the publish panel until you find the sub-section specific to your destination account. This is where you'll enter X/Twitter specific metadata.

When creating a publication to your X/Twitter destination, Wildmoka asks you to choose a sharing type :

  • Native — posts a regular post with the video attached directly to it.
  • Card — posts a link card (title/description/call-to-action) pointing to a hosted page, instead of an attached native video.
  • Studio — uploads the video to your X/Twitter Media Library without posting automatically, so you can manage/schedule it from the platform yourself. This option only shows up if your X/Twitter account has Media Studio access.

Fields available on the X/Twitter destination:

  • Message — the post text, up to 280 characters (roughly 23 reserved for an appended link/CTA). @-mention autocomplete is supported.
  • Title / description — for Native and Studio publishing (title up to 100 characters, description up to 200), plus separate Card title/description fields for Card publishing.
  • Call to action (Card type) — e.g. "Visit site" or "Watch now" with a destination URL.
  • Reply / thread — paste the URL of an existing post to publish your clip as a reply, creating a thread. With the "My Tweets" button, select which existing post this new post should reply to.

  • Geo-restriction — allow-list (whitelist) or block-list (blacklist) the post by country.
     
    If whitelist or blacklist is selected, then enter your list of countries to allow or block:

     

  • Embeddable -  A yes/no toggle that controls whether the posted video is allowed to be embedded (played back) on third-party websites via X's embed/oEmbed mechanism, as opposed to being viewable only on X itself. 
  • Decorator -  A burn-in overlay template applied to the video during encoding. Pick an overlay from the list.
  • Aspect ratio - Defines the crop ratio applied to the video before upload to X/Twitter. 
    Values: Compute from source · 16:9 · 1:1 · 9:16 · 4:3 · 4:5 · 5:4 · 2:3 · 3:4 · 9:8
  • Languages - Audio track selection for multi-audio clips. Pick a language from the list of audio tracks.
  • Subtitle publication - Controls how subtitles are handled. Burn modes permanently embed captions into the video pixels. SRT/EIA modes send captions as a separate data track.
  • Subtitles track - Which subtitle track to use from the clip's available tracks. Values: Default · dynamic per clip.
  • Rendition - Controls the output resolution of the video sent to X/Twitter. Example of values:
    Default (Recommended) · 1080p (Optimal) · 1280p (Upscale) · 720p · 360p · 270p (Fastest)
  • Expiration time - an optional date/time picker to automatically expire (unpublish) the post on X/Twitter.
  • File name -  A text field that lets you override the filename Wildmoka uses when it uploads the video file to X, instead of an auto-generated one. Wildmoka slugifies whatever you enter (strips special characters, spaces become dashes) and enforces a limit of 66 characters, with .mp4 appended automatically.

Video requirements :

Property Limit
Format MP4 (H.264 video / AAC audio recommended)
Duration 0.5–140 seconds for a standard post; longer videos require Amplify/media-library rights. Wildmoka rejects uploads at or above 10 minutes.
File size Up to 512 MB is accepted by Wildmoka's upload step; standard (non-Amplify) posts are capped much lower on the platform side (around 15 MB) — very large files should go through the Studio/Amplify workflow.
Resolution Up to 1920×1080
Aspect ratio Between 1:3 and 3:1
Frame rate Up to 60 fps
Audio Mono or stereo only

 

3. Stream live to X/Twitter

Wildmoka can push a live channel/event directly to your X/Twitter destination. When you add it as a live destination for an event:

  1. Wildmoka requests a live ingest source for your account, which returns a secure ingest endpoint and stream key.
  2. Wildmoka creates a broadcast attached to that source, using your configured region.
  3. When you start the live event in Wildmoka, it publishes the broadcast so it goes live on your profile — optionally with an automatic linked post.
  4. When you stop the event, Wildmoka ends the broadcast and cleans up the source it created.

The Twitter destination  exposes the following controls:

  • Title — Sent to X/Twitter as the broadcast's title when the live goes on air. 
  • Message — Text of the announcement tweet Wildmoka posts once the broadcast is live, with the broadcast's share link appended automatically. Supports @mention autocomplete.
  • Live decorator — Only available when the live event runs in continuous mode (not encode once).
  • Live rendition — Only available when the live event runs in continuous mode (not encode once).
  • Subtitles track — Which subtitle track to use from the stream available tracks. 

Important requirement: the connected account needs an eligible paid subscription to create live broadcasts through the platform's API. If the account isn't on an eligible plan, the broadcast creation is rejected and Wildmoka reports it as a live-publishing failure (see Troubleshooting).

 

4. Monetize or apply policies for X/Twitter

If your connected account has Media Studio / Amplify monetization access, the X/Twitter destination exposes these fields on Native and Studio publications :

  • Amplify program — assign the clip to one of your available ad/monetization programs, or to "Open Amplify."
  • Category allow/deny lists — control which ad categories can run against your content, and block specific advertisers.
  • Monetization geography — monetize in all countries, or restrict monetization to a specific country list.

These fields only appear if the platform itself has granted your account monetization entitlements — Wildmoka reads your account's available programs directly from the platform and cannot create or expand access to them.

Wildmoka also pulls back view counts and earnings for published clips (where available), shown in Wildmoka's clip analytics regardless of which of the two destination types you used to publish.

Content policy: Wildmoka does not moderate or review the content you publish — everything you post is still subject to the platform's own rules. For a post or account to remain eligible for monetization, the platform requires compliance with its Creator Monetization Standards, including:

  • No illegal content, products, or services.
  • No overly suggestive, sexually explicit, or pornographic content.
  • No graphic violence, or hateful conduct targeting people based on protected characteristics.
  • Good standing with the platform's User Agreement, Content Monetization Standards, and (if applicable) Subscriptions/Amplify terms.

Separately, the platform's broader Creator Revenue Sharing program has its own account-level eligibility bar (active Premium/Premium Business/Organization subscription, minimum followers, minimum recent impressions, account age, complete profile, 2FA, etc.) that is entirely managed on the platform's side — Wildmoka has no control over enrollment in that program, and it is the same regardless of which Wildmoka destination type you use.

 

5. X/Twitter troubleshooting

Symptom Likely cause What to do
"Test connection" fails, or publications fail with an authentication error The stored token is no longer valid — usually because access was revoked on the platform's side, or the password changed Re-authorize the X/Twitter destination in Wildmoka
Publish fails immediately, no retry The post was rejected outright (commonly a content-policy rejection) Review the post text/media against the platform's rules; this type of failure is not retried automatically
Upload fails: "Video duration is greater than or equal to 10 min" The source clip is too long for standard upload Trim the clip, or confirm your account has Amplify/media-library rights for longer videos
Upload fails: "Video file is bigger than 512 MB" File exceeds Wildmoka's upload ceiling for this destination Either decrease the rendition or decrease the duration of the video file and republish
Publication is stuck "processing," or fails with a generic processing error The platform's own video-processing pipeline is temporarily erroring on the upload Wildmoka automatically retries this a couple of times; if it still fails, try again later or contact Wildmoka support with the clip/publication ID
Thumbnail looks blank or black Known platform-side glitch when generating the cover image right after upload Wildmoka automatically retries the thumbnail once; if it's still wrong, re-publish or set a custom thumbnail
Publishing/testing slows down or is temporarily refused after several attempts in a short time API rate limits per account/app are being approached — repeated manual "Test connection" clicks or rapid re-publishing can trigger this Wait for the limit window to reset (typically 15 minutes) before retrying; avoid bulk-retrying failed posts back-to-back
Live event fails to go live ("not a premium account" or similar) The connected account does not have an eligible paid subscription for live broadcasting via the API Upgrade the connected account to an eligible plan; this is not something Wildmoka can bypass
Live stream ends unexpectedly The broadcast was ended on the platform's side (manually, by subscription lapsing, or by the platform itself) Check the account's subscription status and the platform's own broadcast status, then restart the live destination in Wildmoka
Card, Studio, Amplify, reply-thread, geo-restriction, or live low-latency/decoration fields are missing from the publish form You are configuring an X destination rather than a Twitter destination — the X destination's form does not currently expose these options in Wildmoka Use a Twitter destination instead if you need these specific options
@mentions you previously used don't autocomplete on this destination Mention history is stored separately per destination type (Twitter vs X), even for the same underlying account Re-enter the mention once on this destination; it will be remembered going forward
Analytics show the clip as "not found" The post was deleted or removed directly on the platform No action needed in Wildmoka; republish if you want the content live again

If an issue persists after trying the relevant step above, contact Wildmoka support with the destination name, the clip ID or live-event ID, and the approximate time of the failure so the team can correlate it with the platform's API responses.

 

Related X Help Center / Developer resources