Truth API: the price, and how to get Trump’s posts in code

Truth API is Trump Media’s paid feed of posts from Truth Social’s top accounts, Donald Trump’s among them. It’s sold by contract to trading firms, and there’s no sign-up page or developer tier.

The posts in it are public, though. Call our API every 2 minutes and each new post reaches your code a minute or two after he posts it, for 720 credits a day.

Truth API is a trading feed, sold by contract

Trump Media announced Truth API in July 2026 as a feed for high-frequency and algorithmic trading firms and switched it on August 1. It covers about 10 of the platform’s top accounts around the clock, with an archive back to 2022, and promises posts in milliseconds. Contracts run $60,000 to $100,000 a month, and about fifteen firms, mostly high-frequency traders, have signed. Institutions ask for it at licensing@tmediatech.com.

Unless software trades on the posts, you don’t need it

Every post in the feed is also public on truthsocial.com, where anyone can read it without logging in. Truth API customers get the same posts; on the earnings call Trump Media’s CEO, Kevin McGurn, described their advantage as getting them “fractionally faster.”

It’s worth it only to software that trades on a post the instant it appears. If that’s you, the email above is the way in. For a news alert or a Slack bot, you need every post, with its images and quotes, a minute after it’s up.

A 2-minute poll gets each new post a minute or so after it’s up

Our user-posts endpoint returns an account’s latest 20 posts as JSON: text, images and video, quotes and ReTruths, and reply, ReTruth and like counts.

curl "https://api.lurkapi.com/v1/truthsocial/user/posts?handle=realDonaldTrump" \
  -H "x-api-key: $LURK_KEY"

To watch the account, call it every 2 minutes and keep the ids you’ve seen. This loop prints the latest 20 on its first run, then each new post as it appears:

API=https://api.lurkapi.com/v1
URL=$API/truthsocial/user/posts
seen=$(mktemp)
while true; do
  curl -sG "$URL" \
    -d handle=realDonaldTrump \
    -d trim=true \
    -H "x-api-key: $LURK_KEY" |
  jq -r '.posts[] | .id+" "+.url' |
  while read -r id url; do
    grep -qx "$id" "$seen" && continue
    echo "$id" >> "$seen"
    echo "$url"
  done
  sleep 120
done

Run like that, his next six posts reached the loop a median of 1 minute 6 seconds after he posted them, and the slowest took 2 minutes 4 seconds. A post goes up somewhere between two polls, and the next poll brings it in:

Every 2 minutes is the right pace: responses are cached for up to 2 minutes, so a faster loop pays twice for the same list.

Check every id: his posts come in bursts, and many have no text

His posts come in clusters, sometimes 15 seconds apart, so one poll often brings two. A script that only compares the newest post with the last one it saw drops the second. Compare every id in the response with the ones you’ve stored, as the loop above does.

Don’t filter on text either. One evening three of his four posts had none: two images and a video. What he posted is in media_attachments, and in quote or reblog when he’s sharing a post. A keyword alert would have missed all three.

If your poller goes down for a few hours, you don’t lose posts. His latest 20 reached back 29 to 36 hours, so the first call after a restart brings everything you missed, unless he posted more than 20 times in between.

Watching one account costs 720 credits a day

Each call is 1 credit, so polling every 2 minutes uses 720 credits a day and 21,600 in a 30-day month: $12.74 a month at Growth pack rates, or $9.72 at Scale. The 100 free credits a new account gets run the loop for three hours.

The same loop watches any public account: pass another handle. Post fetches one post from its link with its current counts, and profile gives an account’s followers and post count; all three are in the Truth Social API docs. For X, the same pattern is in how to monitor a Twitter account.