Best Truth Social APIs & scrapers in 2026

"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 as of October 2026. Re-check each vendor's docs and pricing before you commit budget.

Social Fetch is listed first because it is our product, and because it suits sync REST over public Truth Social profiles and posts, especially if you already normalize social data across TikTok, Instagram, X, or Telegram. Truth Social's own app is the place to publish, DM, or manage an account. Apify or a custom actor suits a one-off crawl shape Social Fetch does not expose. A DIY HTTP or browser client suits teams willing to own auth, pagination, and field drift themselves.

The short list

1. Social Fetch: sync REST for public profiles, profile posts, and single-status lookups.

2. Truth Social app: the first-party route for posting, DMs, and account management.

3. Apify actors: scheduled HTML or browser scrapes for fields outside a typed catalog.

4. Proxy and browser stacks: Bright Data, Oxylabs, Scrapfly, and peers for raw page capture.

5. RapidAPI listings: a discovery marketplace rather than 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 apply the same evaluation criteria to every entry, and I care about production behavior rather than landing-page adjectives. Each entry below carries the same labeled fields: Best for, Strengths, Limitations, and Pricing.

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 and 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, ask whether Truth Social forces a second schema and a second vendor.

7. Compliance fit. First-party tools suit write workflows, and third-party public-data APIs suit enrichment. Read Truth Social's terms for your use case, because I am not your lawyer.

1. Social Fetch

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.

Strengths: Social Fetch exposes three typed routes under /v1/truthsocial, covering 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 catalog, with data.lookupStatus, ISO timestamps, author cards, media and link previews when present, meta.requestId, and meta.creditsCharged. The same API key covers 23 platforms and 232 documented operations, there is an MCP server for AI agents, and new accounts get 100 free credits with no card. Failed lookups are free, and pay-as-you-go credits never expire.

Limitations: Social Fetch covers 23 platforms, not forty, and Truth Social is three routes rather than a full firehose or private-account access. Coverage is public content only, and each Truth Social operation is credit-metered, so confirm meta.creditsCharged. If you need to publish or manage an account, use Truth Social's own tools.

Pricing: from $1.35 per 1,000 credits on the Scale annual plan, or $1.64 per 1,000 on the Scale pack, as of October 2026 on pricing. Endpoint pages: profile, profile posts, and post by URL.

2. Truth Social app

Best for: teams whose job is posting, DMs, notifications, or account settings.

Strengths: Truth Social's own app and web product are the right path for anything that mutates state or requires a logged-in session. Keep first-party tools for creator and operator workflows.

Limitations: it is not a substitute for a metered public enrichment API in your backend, and it gives you no typed handle to JSON path for a multi-network pipeline.

Pricing: a free app account.

3. Apify actors

Best for: teams that need a crawl field Social Fetch does not expose, or a scheduled dump into a dataset.

Strengths: Apify is a scraper runtime where you pick an actor, configure input, poll a run, and download results. That suits research dumps and custom fields.

Limitations: each actor returns its own schema, and polling is awkward as the primary sync path inside a product request handler. See Social Fetch vs Apify for the broader trade-off.

Pricing: a free monthly platform credit, then plans, with compute and per-event fees depending on the actor.

4. Proxy and browser stacks

Best for: teams that only need raw HTML, screenshots, or a one-off capture and will parse the result themselves.

Strengths: Bright Data, Oxylabs, Scrapfly, and similar tools are infrastructure, so you control exactly what gets fetched. They fit a raw page archive kept as compliance evidence.

Limitations: they do not give you a Truth Social profile card with lookupStatus, so you own the parser and the field drift. Look elsewhere when you need one JSON schema across networks.

Pricing: usage-based and set by each provider, so check their pages directly.

5. RapidAPI listings

Best for: weekend discovery of niche endpoints.

Strengths: marketplace listings help you find something fast, with one billing account across publishers.

Limitations: they stop helping when you need three vendors, three schemas, and three billing accounts for one dashboard. See Social Fetch vs RapidAPI when you outgrow the marketplace model.

Pricing: set per listing by each publisher.

Official app vs public enrichment

Truth Social's product remains the place for write workflows, and it does not replace a metered enrichment API for multi-network backends. The split by need looks like this.

• Publish a status, DM, or manage an account: the Truth Social app.

• Resolve @handle to a public profile card from your backend: Social Fetch, or a DIY client if you own the maintenance.

• Page a public profile's posts on a schedule: the Social Fetch profile-posts route.

• Hydrate one status from a public URL: the Social Fetch posts route.

• Custom HTML field nobody documents: an actor or a DIY scrape.

A DIY HTTP or browser client is the remaining option. 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, so budget for breakage if you choose it.

Which option fits which job

• Political or news monitor that already uses Social Fetch for X and Telegram: Social Fetch Truth Social routes.

• Creator posting from a mobile app: the Truth Social app.

• One-off research dump with odd fields: Apify or DIY.

• Agent tool call with the same MCP key as Instagram: Social Fetch MCP or REST.

• Raw page archive for compliance evidence: a proxy and browser stack, then your own parser.

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, while 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