Introduction
To automatically post your articles to X (Twitter) from Newsifier, you need to connect your own X API credentials. This gives you full control over your X account, your API usage, and your billing with X. This article walks you through how to create an X developer account, generate the required API keys, and connect them inside Newsifier.
For general social sharing setup (Facebook, Instagram, Telegram, and other channels), see Social Sharing: How to Share Articles on Multiple Platforms.
What You'll Need
An X (Twitter) account that you want to publish to
Access to the X developer portal to create an app and generate API credentials
Admin or editor access to your Newsifier CMS
Note: X developer account approval can take anywhere from a few hours to a few days. We recommend starting this process in advance so there's no delay in getting your posting up and running.
Step 1: Get Your X API Keys
Ayrshare (the service Newsifier uses for social integrations) has published a complete step-by-step guide covering how to create an X developer account and generate the keys you'll need. Follow their guide here:
In summary, the process involves:
Signing up for an X developer account at developer.twitter.com
Creating a project and an app inside the X developer portal
Generating the API credentials: API Key, API Secret, Access Token, and Access Token Secret
Ensuring your app has Read and Write permissions enabled so it can publish posts on your behalf
Tip: Keep all four credentials in a secure place (for example, a password manager). You'll need all of them in the next step, and some of them can only be viewed once in the X developer portal.
Step 2: Connect Your Keys in Newsifier
Once you have your X API credentials ready:
In the Newsifier CMS, go to General → Settings → Share
Scroll to Twitter Credentials section.
Paste your API Key, API Secret.
Save.
Once saved, return to Newsifier and test the setup by publishing an article with X selected as a sharing platform. The post should appear on your X account, and you can check its status on the Social Posts page in the CMS.
Troubleshooting
X posts are failing after connecting the keys
Check the Social Posts page in the CMS for the specific error message. The most common causes are:
Read-only permissions: Your X app must have Read and Write access. Go back to the X developer portal and verify the permission settings for your app.
Expired or regenerated tokens: If you regenerated your access tokens in the X developer portal after connecting them to Ayrshare, the old tokens stop working. Generate new tokens and update them in the Ayrshare dashboard.
API plan limits: If you're on X's free tier and exceed the monthly post limit, posting will fail until the next billing cycle or until you upgrade your plan.
X has disappeared from the sharing panel
If X is no longer visible as a sharing option in the article editor, your connection may have been unlinked (this can happen if tokens expire or permissions change on the X side). Go to General → Settings → Share → Connect Social and reconnect X. For more on this, see Troubleshooting Social Media Sharing and Ayrshare Issues.
FAQs
Does this affect Facebook, Instagram, or other channels?
No. This setup only applies to X (Twitter). all others continue to work through the standard Newsifier / Ayrshare connection.
How much does an X developer account cost?
X offers a free tier with a limited number of monthly posts, plus paid tiers with higher allowances. Pricing and limits are set by X and can change — check the X developer portal for the current plans.
Can I disconnect or replace my keys later?
Yes. You can disconnect or replace your X credentials at any time from the dashboard (via General → Settings → Share).
Still Having Issues?
If you've followed the steps above and X posting is still not working, contact our support team. Please include:
A screenshot of any error message from the Social Posts page
Confirmation that your X app has Read and Write permissions
The approximate time when the post was attempted
We're happy to help you get things running again.
