Truth Social Profile Scraper

What does Truth Social Profile Scraper do?

The Truth Social Scraper is a robust, automated tool that extracts posts and engagement data directly from Truth Social user profiles. Built on the professional Apify platform using Playwright and Camoufox, it seamlessly interacts with Truth Social's backend API (Mastodon-based) to capture the richest possible JSON structured data while avoiding common bot-blocking challenges.

It extracts posts, texts, interactions (replies, re-truths, likes), and connected media. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. This tool is ideal for political monitoring, market research, and trend analysis.

Why use Truth Social Profile Scraper?

Due to Truth Social lacking a public API, manual data tracking is slow and error-prone. This actor runs stealthily to fetch precise numbers directly from the internal API in real-time. Whether you are tracking Donald Trump's posts or monitoring specific political figures, this scraper offers:

• Speed: Harnessing Playwright with hidden API interception guarantees incredibly fast scraping.
• Reliability: Employs Camoufox stealth technology to bypass fingerprinting.
• Thoroughness: Gathers exact timestamps, high-res media links, and interaction metrics.

How to use Truth Social Scraper

1. Create a free Apify account if you haven't already.
2. Open your Actor on your Apify Console.
3. In the input tab, insert the Truth Social profile URL(s) you wish to scrape (e.g., https://truthsocial.com/@realDonaldTrump) in the Start URLs.
4. (Optional) Adjust the Max posts per profile to restrict the number of extracted posts.
5. Click Start to run the actor.
6. Once the run completes, click on the Storage tab to view your data or export it in various formats.

Input

The scraper accepts the following input settings:

• Start URLs (startUrls): An array of URLs pointing to the target Truth Social profiles (e.g., https://truthsocial.com/@realDonaldTrump).
• Max posts per profile (maxPostsPerProfile): Limits how many posts will be extracted per profile. Set to 0 for unlimited extraction.

Output Structure

The scraper outputs rich JSON data for every post encountered on the user's profile feed:

{
  "id": "112233445566778899",
  "authorUsername": "realDonaldTrump",
  "authorId": "107780283083693356",
  "created_at": "2024-03-01T12:00:00.000Z",
  "url": "https://truthsocial.com/@realDonaldTrump/112233445566778899",
  "contentRawHtml": "<p>MAKE AMERICA GREAT AGAIN!</p>",
  "contentPlainText": "MAKE AMERICA GREAT AGAIN!",
  "replies_count": 3450,
  "reblogs_count": 12000,
  "favourites_count": 55000,
  "media_attachments": [
    "https://static-assets.truthsocial.com/.../video.mp4"
  ],
  "type": "post",
  "rebloggedId": null
}

Data table

Below is a brief overview of the main data fields to expect:

Field	Description
id	The unique Mastodon/Truth Social ID of the post.
authorUsername	The username of who authored the post.
created_at	The exact ISO-8601 timestamp the post was created.
url	A link back to the specific post.
contentPlainText	The cleaned plain-text content of the post.
replies_count	Number of replies.
reblogs_count	Number of re-truths (shares).
favourites_count	Number of likes.
type	Designates if the item was an original post or a re-truth.

Pricing / Cost estimation

This scraper is highly efficient. Running it to collect a few hundred posts typically takes only a few seconds or a minute at most, which ensures it consumes a minute fraction of Apify Compute Units. This means it's extremely affordable to run and testing it will fall well under the free tier limits on Apify.

Tips or Advanced options

• Wait for Network Idle: The actor is specially configured to auto-scroll to the bottom of the feed and pause in order to give Truth Social enough time to respond to API fetches.
• Try to run this scraper on standard resident proxies if you process massive queues to maintain stealth.

FAQ, disclaimers, and support

Is it legal to scrape Truth Social? Extracting public data using automated tools is generally permissible for public research, but you should always review local regulations and the platform's Terms of Service. Be mindful not to overload servers by utilizing massive concurrencies.

If you find any bugs or limitations, please file an issue in the Issues tab.