All tutorials

How to scrape Truth Social posts with Python (2026)

A Python walkthrough for GET /v1/truthsocial/posts. Copy the snippet, run it, then read the JSON.

GET /v1/truthsocial/posts · 2 credits

Also available in

You'll pull a public Truth Social post and see the fields you get back.

Typical job: following up alerts. You have a public Truth Social post URL from a monitor or webhook, and you want its text, author, media and counts. Both /@handle/{id} and /@handle/posts/{id} links work.

Get ready

Create a Social Fetch API key and get Python ready. New accounts include 100 free credits.

The API Keys page in the Social Fetch app. The New API key form is labelled: type a name, then click Create key.
Open API Keys, name the key and click Create key. The full key is shown only once, so copy it straight away.
  • API key. Create a Social Fetch account, open API Keys and create a key. New accounts include 100 free credits.

  • Python setup. Python 3 with requests installed (pip install requests). Set SOCIALFETCH_API_KEY to your key.

When you're done, SOCIALFETCH_API_KEY is set in your shell.

Make the request

Copy the Python sample and run it. It calls GET /v1/truthsocial/posts with your key in the x-api-key header, using this example: /v1/truthsocial/posts?url=https%3A%2F%2Ftruthsocial.com%2F%40justthenews%2F116972401572691045.

Request
Python

It prints the response as a Python dict with data and meta. An error status stops the script at raise_for_status() instead.

Read the response

The response is JSON with two parts: data holds the posts and meta holds creditsCharged and requestId. The sample below is a trimmed copy of a real response; the endpoint page lists every field. Credits are charged on completed lookups, not on failed requests.

The Social Fetch Playground showing a real response from GET /v1/truthsocial/posts with a Just the News post URL. The url field and the metrics block of the response are labelled.
The post's text, author, media and counts are in data.post.
Request
Sample response

Check data.lookupStatus first when the response has one. Keep meta.requestId in case a row looks wrong.

a deleted or missing post returns lookupStatus not_found. This reads one post; for an account's feed use GET /v1/truthsocial/profiles/{handle}/posts with cursor.

You finished

The Playground, the docs and your code all call the same endpoint at the same price. Pick a next step below.

Common questions

Do I need an official Truth Social developer account?

No. Social Fetch authenticates with your Social Fetch API key. You call GET /v1/truthsocial/posts and we handle the lookup. You still need to follow each platform's terms for how you use public data.

What does the Truth Social posts endpoint return?

JSON with two parts: data holds the posts and meta holds creditsCharged and requestId. The endpoint page and the API docs describe every field.

What Truth Social post URL formats work?

Pass the full public post URL as the url query parameter, in the form /@handle/{id} or /@handle/posts/{id}. Check lookupStatus before you read data.post.

Is this the same as listing a profile's posts?

No. This route reads one post by URL. To page through an account's public posts, use GET /v1/truthsocial/profiles/{handle}/posts.

How much does a successful request cost?

2 credits. Failed requests are free.

Is this okay for production?

Yes. It's the same API the Playground and the docs use: typed errors, a requestId on every response, and credits charged only on completed lookups. New accounts get 100 free credits.

Any Python-specific tips for this request?

Yes. Call response.raise_for_status() before response.json(), set a timeout on requests.get, and keep response.json()["meta"]["requestId"] when a row looks wrong.