SocialCrawl

Truth Social data API

Read profiles and posts from Truth Social with one key and one response shape.

Public Truth Social data: profiles, an account's recent truths, and full detail on one post. Posts come back as the same canonical Post object you get from X or Threads.

Your first call

1. Fetch a profile

cURL
curl "https://www.socialcrawl.dev/v1/truthsocial/profile?handle=realDonaldTrump" \
  -H "x-api-key: sc_your_key_here"
TypeScript
const res = await fetch(
  "https://www.socialcrawl.dev/v1/truthsocial/profile?handle=realDonaldTrump",
  { headers: { "x-api-key": process.env.SOCIALCRAWL_API_KEY! } },
);
const { data } = await res.json();
console.log(data.author.display_name, data.author.followers);
Python
import os
import requests

res = requests.get(
    "https://www.socialcrawl.dev/v1/truthsocial/profile",
    params={"handle": "realDonaldTrump"},
    headers={"x-api-key": os.environ["SOCIALCRAWL_API_KEY"]},
)
data = res.json()["data"]
print(data["author"]["display_name"], data["author"]["followers"])

Measured on 22/11/2026: this call returned the account with its follower, following and truth counts for 1 credit. The author.id it returns is the numeric user_id that user/posts accepts.

2. Fetch their content

cURL
curl "https://www.socialcrawl.dev/v1/truthsocial/user/posts?handle=realDonaldTrump" \
  -H "x-api-key: sc_your_key_here"

3. Read computed fields

When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include engagement_rate, language, content_category, and estimated_reach. See Computed fields for formulas, clamping rules, and null semantics. Where an endpoint supports them, list rows also carry judged labels (computed.labels, computed.relevance) by default at no extra credits; see Labels.

What it covers

What you wantCall
Followers count and the numeric idGET /v1/truthsocial/profile
An account's recent truthsGET /v1/truthsocial/user/posts
Likes, retruths and replies on a truthGET /v1/truthsocial/user/posts or GET /v1/truthsocial/post
One truth in fullGET /v1/truthsocial/post

What it does not cover

  • Keyword search. The platform exposes none, so there is no /v1/truthsocial/search and no way to ask who mentioned a topic.
  • Private or protected accounts and anything behind a login are not returned.
  • A separate comments or followers list. Reply counts come back on each truth, not the replies themselves.

Accounts and posts

Run profile first. It is also where you get the numeric user_id. Page deeper through a feed by passing next_max_id from the previous response. Narrow a feed to a window with since and until.

cURL
curl "https://www.socialcrawl.dev/v1/truthsocial/user/posts?handle=realDonaldTrump&next_max_id=ID_FROM_PREVIOUS_PAGE" \
  -H "x-api-key: sc_your_key_here"

Monitoring without a search endpoint

The platform has no keyword search, so monitoring means naming the accounts you care about and walking their feeds. Two composites make that cheaper than it sounds.

EndpointCreditsWhat it returns
GET /v1/prism/truthsocial-pulse20One handle's whole loop: profile, recent posts, a detail drill on the top ones, the news echo, and an activity and sentiment read
GET /v1/prism/voice5One person's posts across X, Threads, Bluesky, and Truth Social merged into a single time-ordered feed

prism/voice is usually the real question when someone posts on more than one network.

All endpoints

3 endpoints available.

EndpointPathCredit Tier
Get Truth Social post details/v1/truthsocial/poststandard (1cr)
Get Truth Social user profile/v1/truthsocial/profilestandard (1cr)
List Truth Social user posts/v1/truthsocial/user/postsstandard (1cr)

How far back and how deep

Each list returns one page at a time. Send cursor for the next page, or max_items or max_pages to collect several pages in one call. A page size appears only where it has been verified. How paging works

PathRows per pageDate windowOne call collects
/v1/truthsocial/user/postsabout 20since and until, applied to each page fetchedup to 5,000 rows or 50 pages

Platform notes

Identifiers split three ways. profile takes a handle, user/posts takes handle or user_id, and post takes a url. Sending user_id is the faster way to read a feed.

user/posts is the only paginated endpoint, and it pages with next_max_id rather than the universal cursor.

trim=true costs the same. It works on user/posts and returns a lighter payload at the same price.

Next steps