# Truth Social User Posts API (https://www.socialcrawl.dev/platforms/truthsocial/user-posts)

> Returns a list of recent truths posted by a Truth Social user. Each truth includes the text content, like count, retruth count, reply count, media attachments, and creation timestamp.

TL;DR: `GET /v1/truthsocial/user/posts` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `handle` | no | Truth Social username without the @ symbol |
| `user_id` | no | Truth Social user id. Use this for faster response times. Trumps is 107780257626128497. It is the 'id' field in the profile endpoint. |
| `next_max_id` | no | Used to paginate to next page |
| `trim` | no | Set to true for a trimmed down version of the response |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

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

## FAQ

### How do I list a Truth Social user's recent truths with the API?

Send a GET request to /v1/truthsocial/user/posts with either a handle (no @ symbol) or a user_id parameter. SocialCrawl returns an array of recent truths including the text, like count, retruth count, reply count, media attachments, and creation timestamp.

### Should I use handle or user_id for faster responses?

Prefer user_id when you already have it. It skips the extra lookup step and returns faster. The user_id comes back in the profile endpoint response. For example, Donald Trump's user_id is 107780257626128497, and passing it beats re-resolving the handle every call.

### How do I paginate through older truths?

The response includes a next_max_id cursor on the last page of results. Pass that value back in as next_max_id on your follow-up request to continue fetching older truths. Keep going until the cursor is empty to reach the full history available upstream.

### What fields does each truth include?

Every truth has its id, text content, like count, retruth count, reply count, media URLs, author info, and created_at timestamp. Field names stay consistent with other SocialCrawl platforms so you can reuse the same processing logic.

### Can I trim the response to save bandwidth?

Yes. Pass trim=true and the endpoint returns a compact payload with only the essential fields. Useful when you are ingesting Truth Social truths at scale into a pipeline and want to minimise bandwidth and parsing overhead on your side.

See the full Truth Social API: https://www.socialcrawl.dev/platforms/truthsocial

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to list Truth Social user posts with an API
- What data does the SocialCrawl Truth Social user/posts endpoint return?