# Truth Social (/docs/truthsocial)



Truth Social [#truth-social]

Truth Social profiles, an account's recent truths, and full detail on one post. Every endpoint is a `GET` and costs **1 credit**, and posts come back as the same canonical `Post` object you get from X or Threads.

Base URL: `/v1/truthsocial/...`

Getting Started [#getting-started]

1\. Fetch a profile [#1-fetch-a-profile]

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

Returns display name, bio, follower and following counts, truth count, and profile image URL.

2\. Fetch their content [#2-fetch-their-content]

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

3\. Read computed fields [#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](/docs/computed-fields.md) for formulas, clamping rules, and null semantics.

What you can get [#what-you-can-get]

* **`GET /v1/truthsocial/profile`** — an account snapshot by `handle`. Run it first; it is also where you get the numeric `user_id`.
* **`GET /v1/truthsocial/user/posts`** — the account's recent truths, each with text, like, retruth and reply counts, media attachments, and creation time. Takes **either `handle` or `user_id`** — one of the two is required. Page deeper by passing `next_max_id` from the previous response.
* **`GET /v1/truthsocial/post`** — one truth in full, addressed by its `url`.

```bash
# Walk back through an account's feed
curl "https://www.socialcrawl.dev/v1/truthsocial/user/posts?handle=realDonaldTrump&next_max_id=ID_FROM_PREVIOUS_PAGE" \
  -H "x-api-key: sc_your_api_key_here"
```

There is no search on Truth Social [#there-is-no-search-on-truth-social]

The platform exposes no keyword search of any kind, so there is no `/v1/truthsocial/search` and no way to ask "who mentioned X". Monitoring means naming the accounts you care about and walking their feeds.

Two things make that cheaper than it sounds. `GET /v1/prism/truthsocial-pulse` (20cr) does the whole loop for one handle in a single call — profile, recent posts, per-post detail drill on the top ones, the news echo, and an activity and sentiment read. And `GET /v1/prism/voice` (5cr) merges one person's posts across X, Threads, Bluesky, and Truth Social into a single time-ordered feed, which is usually the real question when someone posts on more than one network.

Endpoints [#endpoints]

<PlatformEndpoints platform="truthsocial" />

Notes [#notes]

* All endpoints use `GET` method with query parameters
* Authentication via `x-api-key` header
* Responses follow the unified SocialCrawl schema
* `profile` takes a `handle`, `user/posts` takes `handle` **or** `user_id`, and `post` takes a `url`
* `user/posts` is the only paginated endpoint, and it pages with `next_max_id` rather than the universal cursor
* `trim=true` on `user/posts` returns a lighter payload at the same price