All tutorials

How to scrape Truth Social profiles with curl (2026)

A curl walkthrough for GET /v1/truthsocial/profiles/{handle}. Copy the snippet, run it, then read the JSON.

GET /v1/truthsocial/profiles/{handle} · 2 credits

Also available in

You'll pull a public Truth Social profile and see the fields you get back.

Typical job: monitoring political accounts. Check that each public Truth Social handle exists, store its follower counts (data.profile.metrics) and verification, then fetch posts (/profiles/{handle}/posts) only for the accounts you still track. Check lookupStatus: not_found is an answer, not an empty object.

Get ready

Create a Social Fetch API key and get curl ready. New accounts include 100 free credits.

The API Keys page in the Social Fetch app. The New API key form is labelled: type a name, then click Create key.
Open API Keys, name the key and click Create key. The full key is shown only once, so copy it straight away.
  • API key. Create a Social Fetch account, open API Keys and create a key. New accounts include 100 free credits.

  • curl setup. Any shell with curl. Set SOCIALFETCH_API_KEY to your key (export SOCIALFETCH_API_KEY=sfk_…) before you run the sample.

When you're done, SOCIALFETCH_API_KEY is set in your shell.

Make the request

Copy the curl sample and run it. It calls GET /v1/truthsocial/profiles/{handle} with your key in the x-api-key header, using this example: /v1/truthsocial/profiles/realDonaldTrump.

Request
curl

It prints the JSON response. With -sS, curl stays quiet on success but still prints connection errors.

Read the response

The response is JSON with two parts: data holds the profiles and meta holds creditsCharged and requestId. The sample below is a trimmed copy of a real response; the endpoint page lists every field. Credits are charged on completed lookups, not on failed requests.

The Social Fetch Playground showing a real response from GET /v1/truthsocial/profiles/{handle} with the handle realDonaldTrump. The handle field and the metrics block of the response are labelled.
Follower, following and post counts are in data.profile.metrics.
Request
Sample response

Check data.lookupStatus first when the response has one. Keep meta.requestId in case a row looks wrong.

this returns the profile only; posts are a separate call. Pass the username with or without @. Each lookup costs 2 credits, so check lookupStatus before you fetch more.

You finished

The Playground, the docs and your code all call the same endpoint at the same price. Pick a next step below.

Common questions

Do I need an official Truth Social developer account?

No. Social Fetch authenticates with your Social Fetch API key. You call GET /v1/truthsocial/profiles/{handle} and we handle the lookup. You still need to follow each platform's terms for how you use public data.

What does the Truth Social profiles endpoint return?

JSON with two parts: data holds the profiles and meta holds creditsCharged and requestId. The endpoint page and the API docs describe every field.

Does the Truth Social profile endpoint return posts?

No. This route returns the profile only. For recent posts use GET /v1/truthsocial/profiles/{handle}/posts. For a single post by URL use GET /v1/truthsocial/posts.

What does not_found mean on a Truth Social profile?

not_found means no public account has that handle, and data.profile is null. HTTP 200 still means the request finished. Check lookupStatus before you treat the response as a profile.

How much does a successful request cost?

2 credits. Failed requests are free.

Is this okay for production?

Yes. It's the same API the Playground and the docs use: typed errors, a requestId on every response, and credits charged only on completed lookups. New accounts get 100 free credits.

Any curl-specific tips for this request?

Yes. Pass the key with -H "x-api-key: $SOCIALFETCH_API_KEY", and wrap the full URL in double quotes so the shell doesn't split it at the & between query parameters. -sS hides the progress meter but still shows connection errors. curl doesn't treat an HTTP error status as a failure, so read the error JSON it prints, or add --fail-with-body.