X API read controls: pause, frequency, and lookback (pay-per-use X bills every read)
Completed ClosedWhat problem does this solve?
X's pay-per-use API bills every read, and reads draw from the same credit balance and spend cap as posting. With multiple X accounts connected, Mixpost's background X analytics imports cost us quite a bit, with zero posts published yet. At that rate, reads alone would hit our spend cap mid-month and block publishing. There is currently no way to control or even see this read volume from inside Mixpost.
Describe the solution
Admin controls for X API usage, set globally and per X account:
- Pause/disable X analytics and audience imports.
- Set X import frequency (e.g., hourly / daily / weekly / manual only).
- Limit the lookback window (e.g., only refresh metrics for posts from the last 7 days, or the last N posts).
- Show daily X API usage (reads/writes) in the Admin Console.
Alternatives considered
- Lowering the X spend cap: stops the reads, but also blocks publishing once the cap is hit.
- Disabling the Laravel scheduler's import jobs: stops analytics for all providers, not just X.
- Disconnecting X accounts: stops the cost, but also stops X publishing.
- Patching Mixpost's code locally: lost on every update and hard to maintain.
Completed
Add controls for X API usage
X analytics imports incur substantial read charges when multiple X accounts are connected, even before any posts are published. These charges consume the same credit balance and spend cap used for posting; implement controls for X API usage, including analytics imports and other API operations.
Voters (2)
This topic has been linked to the roadmap item "Add controls for X API usage".
This discussion was closed 1 hour ago and no longer accepts replies. Start a new topic