Truth Social Post API
Pass a public Truth Social status URL and get text, author, media, and engagement in the shared Social Fetch JSON envelope.
GET /v1/truthsocial/posts2 credits per successful request.
About this endpoint
Alerting tools, CRM notes, and newsroom workflows often already have a Truth Social permalink — not a handle feed to page. What they need next is one structured row: body text, who posted it, media or a link card, and engagement counts when public. Parsing status URLs by hand across `/@handle/{id}` and `/@handle/posts/{id}` shapes is busywork that breaks when the product adds another path.
`GET /v1/truthsocial/posts` takes a required public post `url` query param. Send `x-api-key` and branch on `data.lookupStatus` before you write — `found` or `not_found`. On `found`, read `data.post` for id, canonical url, ISO timestamps, text, author snapshot, metrics, media, link previews, polls, and quote summaries when Truth Social exposes them. Accepted public status URL shapes include `/@handle/{id}` and `/@handle/posts/{id}` on truthsocial.com.
This route is one post by URL. To page a handle's feed use `GET /v1/truthsocial/profiles/{handle}/posts`. For the profile card alone, use `GET /v1/truthsocial/profiles/{handle}`. Pricing is on the credit badge for this operation; bill from `meta.creditsCharged` on every response.
Truth Social Post API FAQ
How do I fetch a Truth Social post by URL?
Call GET /v1/truthsocial/posts with your Social Fetch API key in the x-api-key header and a public status url query param. Read data.lookupStatus, then data.post when the status is available. Full parameters and examples are in the API docs linked from this page.
How many credits does a Truth Social post lookup cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
What URL formats does the Truth Social post endpoint accept?
Pass a full public Truth Social status URL. Supported path shapes include /@handle/{id} and /@handle/posts/{id} (for example https://truthsocial.com/@handle/123… or …/@handle/posts/123…). Profile pages belong on GET /v1/truthsocial/profiles/{handle}.
What fields are in the Truth Social post response?
When lookupStatus is found, data.post can include id, url, createdAt, editedAt, text, spoilerText, language, visibility, isSensitive, author, reply and quote ids, metrics, media, linkPreview, poll, and quote summary when Truth Social shows them.
What happens when a Truth Social post URL is not found?
lookupStatus of not_found means Social Fetch could not return a public status for that URL. data.post is null. Keep meta.requestId if you need support on that row. HTTP 200 only means the request finished.
Post by URL vs profile posts vs profile card?
Use GET /v1/truthsocial/posts when you already have a status permalink. Use GET /v1/truthsocial/profiles/{handle}/posts to page posts for a username. Use GET /v1/truthsocial/profiles/{handle} for the identity card. They are separate operations on the Truth Social hub.
Do I need a Truth Social login to fetch a post?
No. You authenticate to Social Fetch with an API key. The route reads publicly visible statuses; it does not require a Truth Social session or act on behalf of a logged-in user.