Truth Social API

Available endpoints

The social service exposes public Truth Social data through ScrapeCreators. Every route is protected by x402 and returns the upstream JSON response without inventing a second response format.

• GET /v1/social/truthsocial/profile looks up a profile by handle.
• GET /v1/social/truthsocial/user-posts returns a user's posts with pagination support.
• GET /v1/social/truthsocial/post fetches one post from its canonical Truth Social URL.

Use the generated API reference for current prices, query parameters, and response statuses.

Fetch a profile

Pass the username without an @ prefix:

GET /v1/social/truthsocial/profile?handle=realDonaldTrump

The service normalizes handles for caching. Profile results are cached briefly to reduce upstream latency without keeping stale profile data for long periods.

Fetch user posts

Identify the account with either handle or userId. At least one is required.

GET /v1/social/truthsocial/user-posts?handle=realDonaldTrump&trim=true

Set trim=true for a smaller response when the upstream supports it. To request the next page, pass the returned pagination cursor as nextMaxId:

GET /v1/social/truthsocial/user-posts?userId=107780257626128497&nextMaxId=114315219437063159

First-page timelines use a short cache lifetime. Paginated historical results are cached longer because they change less frequently.

Fetch one post

Pass the complete public post URL as an encoded url query parameter:

GET /v1/social/truthsocial/post?url=https%3A%2F%2Ftruthsocial.com%2F%40realDonaldTrump%2Fposts%2F114315219437063160

URL fragments are removed before cache lookup. Invalid URLs fail validation before an upstream request is made.

Errors and retries

Validation failures return 400. Upstream authentication, policy, missing-resource, rate-limit, and availability errors may return 401, 403, 404, 429, or 503. Retry only transient 429 and 503 responses, preserve the payment identifier, and use exponential backoff.

The service degrades gracefully when its cache is unavailable: requests continue to the upstream provider and cache failures are recorded in structured logs.