Truth Social API Options in 2026: What Exists and What Works

November 8, 2026

Journalists, researchers and market analysts all track Truth Social, because a single post can move a news cycle or a stock. If you want that data in code, the options are thin. This guide lays out what exists in 2026, what each option needs, and a simple recipe for monitoring accounts reliably.

Is there an official Truth Social API?

We found no public developer program, API key signup or API documentation from Truth Social. We also could not read Truth Social's own pages on 8 November 2026: its site refused our checker, so this post does not quote its terms. Read Truth Social's terms of service yourself before you collect anything, and treat every unofficial route as something that can change without notice.

Option 1: truthbrush, the open-source client

truthbrush is a Python client first published under the stanfordio GitHub organization. Its README says it is designed for academic research, open source intelligence and data archival, and lists what it can pull:

• Search for users, statuses, groups or hashtags.
• A user's statuses and metadata.
• Trending posts, hashtags and groups, plus suggested users.
• Ads, likes on a post and comments on a post.
• Posts from a group timeline.

Things to know before you use it:

• It wants an account. You set a Truth Social username and password as environment variables, or a login token.
• Public mode is partial. A --no-auth flag runs only endpoints readable without login. The README warns that which endpoints are public is decided by Truth Social and may change.
• The original repo is archived. Its README points to a maintained fork at w2rc/truthbrush.

pip install truthbrush
truthbrush --no-auth user realDonaldTrump

Option 2: a data API

A hosted API saves you from managing a Truth Social account, login tokens and breakage. You trade some flexibility for a stable JSON shape and someone else on call when things change.

Options compared

A monitoring recipe

Most Truth Social projects watch a fixed list of accounts. Here is a design that does not miss posts and keeps a clean record.

1. Poll on a schedule. Fetch each account's latest posts every 1 to 5 minutes, depending on how fast you must react.
2. Deduplicate by post ID. Store IDs you have seen; only new IDs trigger alerts.
3. Store more than the text. Keep post ID, URL, created time in UTC, your capture time, text, media URLs, and reply, repost and like counts.
4. Re-read recent posts. Fetch each post again after 1 hour and 24 hours. Compare text to catch edits, and record a 404 as a possible deletion with its time.
5. Measure latency. Log capture time minus created time. If it creeps up, poll faster or alert on failures.
6. Keep the raw response. Store the JSON you received, so later questions can be answered without a re-pull.

Budget it: one account polled every 2 minutes is 720 calls a day, about 21,600 a month. At ScrapeIO's Starter rate that is about $41; at the Growth rate about $21. Repeats that hit the cache are not charged.

Responsible use

• Stick to public accounts and public posts.
• Quote accurately and link to the original post.
• If you publish an archive, say how and when you collected it.
• This is not legal advice. Check the platform's terms and your local law for your use.

Doing it with ScrapeIO

The recipe maps to three endpoints: the Truth Social profile API, the Truth Social user posts API, which pages back with next_max_id, and the Truth Social post API for re-reading a single post. No Truth Social account is needed. See the Truth Social endpoints.

curl "https://scrapeio.com/v1/truthsocial/user/posts?handle=realDonaldTrump" -H "x-api-key: YOUR_KEY"

Sources

Checked on 8 November 2026 from each vendor's own pages. Prices and limits change; follow the links before you decide.

• https://github.com/stanfordio/truthbrush
• https://github.com/w2rc/truthbrush