Truth Social API

Scrape Truth Social data with one API

Name: Truth Social Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Truth Social data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/truthsocial

3 active endpoints

GET /v1/truthsocial/profile
GET /v1/truthsocial/user/posts
GET /v1/truthsocial/post

What Truth Social endpoints does SocialCrawl ship?

3 live read endpoints for public Truth Social data. Profiles, user posts, and single posts. Data API only.

Profile

1 credit

/v1/truthsocial/profile

Get Truth Social user profile.

handle

User posts

1 credit

/v1/truthsocial/user/posts

List Truth Social user posts.

handle, user_id, next_max_id, trim

Post

1 credit

/v1/truthsocial/post

Get Truth Social post details.

url

Truth Social API3 endpoints supported

View docs

Returns a Truth Social account's public profile: display name, bio, follower and following counts, truth count, and profile image URL.

Use it when you have a handle and want the account snapshot before pulling its posts.

1 credit

GET/v1/truthsocial/profile?handle=realDonaldTrump

handle

handle · Truth Social username without the @ symbol

$ curl https://www.socialcrawl.dev/v1/truthsocial/profile?handle=realDonaldTrump \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Truth Social API works

Truth Social is a normal SocialCrawl social surface. You call GET /v1/truthsocial/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/truthsocial/profile

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/truthsocial/user/posts

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/truthsocial/post

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/truthsocial/post

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/truthsocial/profile
  ?handle=realDonaldTrump
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorprofile

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postuser/posts

items[].post with id, url, content, engagement, author, published_at, ext

CommentListpost

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediapost

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Truth Social is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Truth Social is for this API

Public Truth Social surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

public profile / channel→ author.*profile identity and counters

public post / media→ post.* / items[].postpost content and engagement

list / search page→ items[] or hitscomments or search hits when present

What this API is used for

The jobs this API is most often used for.

3active Truth Social endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Political and public-figure narrative monitoring

Callers concentrate on profile, content lists, search, and deepen paths on Truth Social. Structured Truth Social JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the Truth Social API

The jobs Truth Social data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

News and OSINT monitoringSingle-account monitoring of public-figure profiles. Narrow by design, and precisely what it is used for.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Truth Social. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Truth Social.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/truthsocial/profile?handle=realDonaldTrump" \
  -H "x-api-key: sc_your_api_key_here"

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

Truth Social on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Truth Social API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProfileGet Truth Social user profile User PostsList Truth Social user posts PostGet Truth Social post details

Comparison

How does SocialCrawl compare to Official Truth API (Trump Media) for Truth Social data?

Same Truth Social data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	Official Truth API (Trump Media)
Who it serves	Developers who need public Truth Social data in their apps	Financial institutions licensing a market-data feed for trading systems
Getting access	Self-serve: sign up and send one GET request with an x-api-key	Enterprise licensing conversation with Trump Media, launched August 1, 2026
Pricing	1 credit per request; 100 free credits on signup, no card	Not published self-serve; licensing reportedly pitched at up to $100k per month
Data coverage	Any public profile, user post timeline, and post detail on Truth Social	A curated real-time feed of market-moving posts from top accounts
Response format	Unified JSON shared across 51 platforms	Market-data feed formats aimed at financial data pipelines
Use cases	Research, monitoring, dashboards, sentiment, app features	Algorithmic trading signals on a licensed subset of accounts

Who it serves

SocialCrawl

Developers who need public Truth Social data in their apps