What is the X post limit per day, and do scheduled posts count?
X's official API documentation, checked on 21 November 2026, does not publish an account-level “posts per day” number. What it does publish for creating a post (POST /2/tweets) is 100 requests per user per 15 minutes and 10,000 requests per app per 24 hours. A scheduled post that Auto X publishes is one of those API requests, so it counts toward the official per-user cap. X's Help Center page on account limits could not be re-read on that date, because it returned a bot challenge, and this guide does not invent a daily account figure.
What is the official X post limit per day?
The official number you can check today is not a daily account cap. It is the create-post rate limit: 100 requests per user every 15 minutes, and 10,000 requests per app every 24 hours, on POST /2/tweets. Those figures come from X's API rate-limits documentation, checked on 21 November 2026. If X shows you a different limit inside the app, treat that in-product message as the account rule for that day.
The table below marks each row as official, or as not published in the developer docs we could read today. X can change limits without notice, so re-check the live rate-limits page and the Developer Console before you raise a queue.
| Limit | Number | Applies to | Status and source, checked 2026-11-21 |
|---|---|---|---|
Create a post (POST /2/tweets) | 100 per 15 minutes | Per user, with a user token | Official: X API rate limits |
Create a post (POST /2/tweets) | 10,000 per 24 hours | Per app | Official: the same rate-limits page |
| Account-level posts per day | Not published in those docs | The posting account | Not in the developer rate-limits table; the X Help Center limits page returned a bot challenge and could not be re-read |
| Premium or verified daily cap | Not published in those docs | Premium or verified accounts | The developer docs checked today do not give a separate daily number |
Rate limits and billing are separate in those same docs: staying inside a rate window does not tell you what a pay-per-usage call will cost. For how a scheduler should read the x-rate-limit-limit, x-rate-limit-remaining and x-rate-limit-reset headers, see our guide to X API rate-limit budgets for Telegram schedulers.
Do scheduled posts count toward X's limits?
Yes. A scheduled post counts as one create-post request when it is published, because the scheduler calls POST /2/tweets from your connected account. X's rate-limits documentation does not give tools a separate allowance. Auto X publishes each queued item as one original post, with up to one photo or video attached, and it does not post replies.
Auto X's own plan limits sit on top of X's and are a separate thing. On the Auto X homepage, checked on 21 November 2026, the Free plan is €0, with text and media scheduling, a 7-day horizon and 10 media posts a month. Pro is €0.99 a month and adds post loops, extended limits and an ad-free bot. Ultra starts at €5.99 a month (Ultra Text €5.99, Ultra Image €7.99, Ultra Video €15.99). None of those plans changes the official X API caps for your account.
Worked example: eight due posts in one 15-minute window
Take a shop that has eight original posts due between 14:00 and 14:14 UTC. Auto X's publisher runs every 5 minutes, so in that official 15-minute user window it can take about three turns at posts that are already due. Eight successful POST /2/tweets calls would use 8 of the official 100 per-user requests in the window, which is well under the cap.
If X refuses a call with HTTP 429, the official docs say the window clears at the Unix time in the x-rate-limit-reset header. Auto X does not drop the post. The item stays scheduled, the publisher retries it on the next 5-minute run, and the bot messages you in Telegram on the first failure and on every 10th attempt, with the error text and a reminder to use /queue or /cancel. /queue lists the last error and the attempt count. For a time-sensitive post, such as a sale that ends at a fixed hour, cancel and reschedule rather than letting it go out late. Our guide on why a scheduled post did not go out on X covers the other common causes of a failed publish.
The 15-minute queue check
The 15-minute queue check is a short method for reading your Auto X queue against the official create-post window, not against an invented daily total.
- Count the next window. Open
/queueand count how many original posts are due in the next 15 minutes, using the times the queue shows. - Compare that count with 100. The official per-user cap is 100 create-post requests in that window. A small shop queue will usually be far below it. If a burst is close, spread the due times before they hit the publisher.
- Leave room for retries. A refused post is tried again on the next 5-minute run. A cluster of retries at the start of a new window can use the new window quickly, so drain a backlog in schedule order rather than firing everything at once.
- Do not add extra accounts to dodge a cap. X's rules on automation and platform manipulation apply to that. Read what X's rules allow for automation before you try it. A sustainable posting pace also helps; see our guide to a sustainable X posting cadence.
Where Auto X fits
Auto X is a Telegram bot that schedules and auto-publishes your text and media posts to X. It does not raise X's official API caps. It spreads posts across the day, keeps a refused post in the queue, and tells you when X returns an error. You can start in Telegram with the @auto_x_schedule_bot Telegram bot.
FAQ
How many posts can you make per day on X?
X's official API documentation, checked on 21 November 2026, does not publish an account-level posts-per-day number. It does publish a create-post cap of 100 requests per user per 15 minutes and 10,000 per app per 24 hours. This guide does not invent a daily account figure, because the Help Center limits page could not be re-read that day.
Do scheduled posts count toward X's limits?
Yes. A scheduler publishes from your account with POST /2/tweets, so each scheduled post uses one of the official per-user create-post requests, just like any other API publish from that account. The developer docs do not give schedulers a separate allowance.
What happens if Auto X hits an X limit?
The post stays in your queue and Auto X retries it every 5 minutes until X accepts it or you cancel it. You get a Telegram message on the first failure and on every 10th attempt, with the error text X returned.
Is there an official daily cap for Premium accounts?
Not in the developer rate-limits documentation checked on 21 November 2026. That page lists the create-post caps above and does not publish a separate daily number for Premium or verified accounts.
Do Auto X plan limits replace X's API caps?
No. The Free plan's 7-day horizon and 10 media posts a month, and the paid plan prices on the Auto X homepage, are Auto X limits. They sit on top of X's official API caps and do not raise them.
Sources
- X API documentation: rate limits (checked 2026-11-21)
- X API documentation: manage posts (checked 2026-11-21)
- X Help Center: X limits (returned a bot challenge; not re-read on 2026-11-21)
- Auto X homepage: plans and prices (checked 2026-11-21)
Educational product guidance. X API rate limits and any in-app account rules can change; re-verify on official documentation before you rely on a number. Last verified 2026-11-21.