"Truth Social API" usually means one of three jobs: post or manage an account inside Truth Social's own product, enrich public profiles and statuses from a backend you already ship, or dump HTML through a generic scraper when you do not care about a stable schema.

Those are different products. Mixing them up is how you end up wiring a second auth story for one network while the rest of your pipeline already speaks one REST key — or paying Actor runtime fees for a single handle lookup your UI could await in one HTTP call.

This is a coverage and ergonomics comparison for July 2026. Re-check each vendor's docs and pricing before you commit budget.

Social Fetch is my pick for sync REST over public Truth Social profiles and posts, especially if you already normalize social data across TikTok, Instagram, X, or Telegram. Prefer Truth Social's own product when you need to publish, DM, or manage an account. Prefer Apify (or a custom actor) when you need a one-off crawl shape Social Fetch does not expose. Prefer a DIY HTTP or browser client only when you are willing to own auth, pagination, and field drift yourself.

The short list

1. Social Fetch — sync REST for public profiles, profile posts, and single-status lookups
2. Truth Social (first-party app / web) — posting, DMs, and account management
3. DIY HTTP / browser clients — self-hosted scrapers against public pages when you own the maintenance
4. Apify / custom actors — scheduled HTML or browser scrapes for fields outside a typed catalog
5. Generic proxy + browser stacks — Bright Data, Oxylabs, Scrapfly, and peers when you only need raw page capture
6. RapidAPI listings — discovery marketplace, not one production contract

Full Truth Social route list and examples live on the Truth Social platform page. Hands-on walkthrough: How to scrape Truth Social data.

How I rank Truth Social data APIs

I care about production behavior, not landing-page adjectives:

1. What you can actually call — profile by handle, cursor-paginated posts, single status by public URL. Count real paths, not "Truth Social support" on a marketing grid.
2. Access gate — instant API key vs account login vs actor configuration. Public enrichment should not require a Truth Social session cookie in your product path.
3. Sync vs async — one HTTP response you can await in a product request, or start-a-run / poll-a-dataset.
4. Typed misses — lookupStatus: not_found beats an empty 200 that looks like a blank page.
5. Error shape — typed outcomes and a requestId beat silent HTML.
6. Multi-platform tax — if your app already pulls TikTok and Instagram, does Truth Social force a second schema and a second vendor?
7. Compliance fit — first-party tools for write workflows; third-party public-data APIs for enrichment. Read Truth Social's terms for your use case. I am not your lawyer.

Ranked picks

1. Social Fetch — public Truth Social over one REST key

Best for product teams and agents that need public Truth Social profiles and posts beside other networks, without a Truth Social login in the request path.

Social Fetch exposes three typed routes under /v1/truthsocial: profile by handle, cursor-paginated profile posts, and a single post by public status URL. Every response uses the same { data, meta } envelope as the rest of the marketplace — data.lookupStatus, ISO timestamps, author cards, media and link previews when present, meta.requestId, and meta.creditsCharged.

Authenticate with x-api-key. New accounts get 100 free credits. Each Truth Social operation is credit-metered (confirm meta.creditsCharged). Coverage is public content only.

Watch for: three routes, not a full firehose or private-account access. If you need to publish or manage an account, use Truth Social first-party tools. Endpoint pages: profile, profile posts, post by URL.

2. Truth Social first-party — write and account workflows

Best when the job is posting, DMs, notifications, or account settings.

Truth Social's own app and web product are the right path for anything that mutates state or requires a logged-in session. That is not a substitute for a metered public enrichment API in your backend. Keep first-party tools for creator and operator workflows; keep a data API for handle → JSON enrichment.

3. DIY HTTP and browser clients

Best when you are willing to own field drift, auth, rate limits, and HTML parsers yourself.

A personal script that hits public Truth Social pages can work until login walls, rate limits, or markup changes show up without a changelog. That path is rarely enough for a multi-platform product that wants one error shape, one credit meter, and one support requestId across Instagram and Truth Social. If you choose DIY, budget for breakage when public pages change.

4. Apify and custom actors

Best when you need a crawl field Social Fetch does not expose, or a scheduled dump into a dataset.

Apify is a scraper runtime: pick an actor, configure input, poll a run, download results. Each actor returns its own schema. Fine for research dumps. Awkward as the primary sync path inside a product request handler. See Social Fetch vs Apify for the broader tradeoff.

5. Generic proxy and browser stacks

Best when you only need raw HTML, screenshots, or a one-off capture and will parse yourself.

Bright Data, Oxylabs, Scrapfly, and similar tools are infrastructure. They do not give you a Truth Social profile card with lookupStatus. Buy them when you need proxies; look elsewhere when you need one JSON schema across networks.

6. RapidAPI listings

Best for weekend discovery of niche endpoints.

Marketplace listings help you find something fast. They stop helping when you need three vendors, three schemas, and three billing accounts for one dashboard. Keep RapidAPI for exploration. See Social Fetch vs RapidAPI when you outgrow the marketplace model.

Official app vs public enrichment

Social Fetch does not replace Truth Social's product for write workflows. Truth Social's product does not replace a metered enrichment API for multi-network backends.

Which option fits which job

Questions before you buy

1. Do you need to write to Truth Social, or only read public pages? That fork decides first-party vs enrichment first.
2. Will Truth Social sit beside other networks? If yes, prioritize one schema and one key.
3. Sync or batch? Product handlers prefer sync. Overnight dumps can live on actors.
4. Do credits expire? Spiky research sprints hate monthly resets.
5. Can you preview without shipping? Use the playground or free credits before you lock a vendor.
6. What happens on a missing handle? Prefer typed not_found over empty HTML.

Frequently asked questions

Is there a Truth Social API for public profiles?

Yes. Social Fetch provides GET /v1/truthsocial/profiles/{handle}, profile posts, and post-by-URL under /v1/truthsocial. Authenticate with a Social Fetch API key. Details: /platforms/truthsocial.

How do I use Truth Social data in a product?

Call the typed REST routes (or MCP tools) for public enrichment, branch on data.lookupStatus, and store meta.requestId for support. For a step-by-step with curl and the SDK, see How to scrape Truth Social data.

Does Social Fetch require a Truth Social login?

No. You need a Social Fetch API key. Coverage is public profiles and statuses only.

Can I access private or locked Truth Social accounts?

No on Social Fetch. Restricted or missing targets resolve through data.lookupStatus (for example not_found) rather than inventing empty post lists.

Truth Social scraper vs official app — which should I use?

Use the official app when you need to post or manage an account. Use a managed public-data API when you need enrichment without Truth Social session cookies in your product path, or when multi-platform schema and sync REST matter more than first-party write scopes.

Smoke-test a handle in the playground, or start with 100 free credits on pricing. Platform hub: /platforms/truthsocial. Broader roundup: Best social media scraping APIs in 2026.