GETTR Scraper: Profiles, Posts, Timelines & Search

At a glance: what it does is extract public GETTR profiles, posts, timelines, and search results; input examples include GETTR URLs, usernames, and search terms; output examples are post and user rows; use cases include monitoring and journalism; limitations, troubleshooting, and pricing/cost notes are covered below.

GETTR Scraper extracts public GETTR profiles, posts, timelines, search results, hashtags, media URLs, author details, and engagement metrics for researchers, analysts, journalists, brand monitoring teams, and data workflows on Apify.

Use this Actor as a GETTR profile scraper, GETTR post scraper, GETTR timeline scraper, GETTR search scraper, or public GETTR data scraper when you need structured data without logging in or running a browser.

Main use cases

• Monitor public GETTR posts mentioning brands, people, topics, campaigns, or hashtags.
• Collect profile and timeline data for OSINT, journalism, social media intelligence, or compliance research.
• Build datasets for NLP, sentiment analysis, entity extraction, and influence analysis.
• Track public account metadata, follower counts, profile text, media links, and post engagement.
• Export public GETTR data to JSON, CSV, Excel, XML, RSS, or downstream Apify integrations.

What data can it extract?

The Actor can save two record types: post and user.

Post records can include:

• post ID and canonical GETTR URL
• text, language, creation time, update time, and post type
• likes, reposts, replies, and views when GETTR provides them
• hashtags, tagged users, image URLs, video URLs, video duration, and video dimensions
• link preview metadata
• author username, display name, bio, website, profile image, follower counts, badges, and verification status

User records can include:

• username, user ID, display name, bio, location, website, and language
• follower and following counts
• verification status, badges, creator metadata, premium flag, and pinned post IDs
• profile image and banner image URLs
• creation and update timestamps when available

Input configuration

Provide at least one GETTR URL, username, or search term. You can combine them in one run.

Field	Description
startUrls	GETTR profile, post, or search URLs. Plain usernames also work.
usernames	GETTR usernames to scrape. The @ prefix is optional.
searchTerms	Keywords or hashtags to search on GETTR.
maxItems	Maximum number of post/profile records to save across all inputs. The Actor caps this at 5,000 per run.

Example input

{
  "startUrls": [
    "https://gettr.com/user/support",
    "https://gettr.com/post/p2bipx0ac19"
  ],
  "usernames": ["milesguo"],
  "searchTerms": ["news", "#politics"],
  "maxItems": 100
}

Example output

{
  "type": "post",
  "source": "search_posts",
  "query": "news",
  "id": "p40659a27cf",
  "url": "https://gettr.com/post/p40659a27cf",
  "text": "Example GETTR post text...",
  "language": "en",
  "createdAt": "2026-05-18T10:00:07.428000+00:00",
  "likeCount": 124,
  "repostCount": 18,
  "replyCount": 7,
  "viewCount": 46182,
  "hashtags": ["news"],
  "imageUrls": ["https://media.gettr.com/group/example/image.png"],
  "videoUrls": ["https://media.gettr.com/group/example/out.mp4"],
  "authorUsername": "exampleuser",
  "authorDisplayName": "Example User",
  "authorFollowersCount": 3121,
  "authorIsVerified": false
}

{
  "type": "user",
  "source": "profile",
  "query": "support",
  "id": "support",
  "username": "support",
  "displayName": "Support & Help",
  "bio": "GETTR Support (Official Account)",
  "website": "https://support.gettr.com",
  "followersCount": 4105293,
  "followingCount": 1,
  "verificationStatus": "VERIFIED",
  "isVerified": true,
  "profileImageUrl": "https://media.gettr.com/group/example/avatar.png"
}

How to run on Apify

1. Open the Actor in Apify Console.
2. Add GETTR profile URLs, post URLs, usernames, or search terms.
3. Set maxItems to the number of records you need.
4. Start the run.
5. Open the Dataset tab to preview and export results.

For larger runs, start with a smaller maxItems value and increase it after confirming that the output matches your workflow.

Exporting results

Results are saved continuously to the default Apify Dataset while the Actor runs. You can download or integrate them as:

• JSON or JSONL
• CSV
• Excel
• XML
• RSS
• HTML table
• Apify API, webhooks, schedules, and integrations

Because records are pushed during scraping, partial results remain useful if a long run is stopped or times out.

Use with the Apify API

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run_input = {
    "usernames": ["support", "milesguo"],
    "searchTerms": ["news"],
    "maxItems": 100,
}

run = client.actor("thescrapelab/Apify-Gettr-Scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits and caveats

• The Actor extracts public GETTR data only.
• It does not access private, deleted, logged-in-only, or restricted content.
• GETTR uses undocumented web endpoints that can change without notice.
• Search result volume can vary by keyword, hashtag, language, region, and current GETTR behavior.
• Some records may not include every field because GETTR does not return every field for every post or profile.
• Very broad searches may need multiple focused runs rather than one large mixed input.

Troubleshooting

Problem	What to try
No results	Check spelling, try a known public username, remove unusual punctuation, or test with support.
Search returns profiles instead of posts	GETTR sometimes returns profile search more reliably than post search for a term. Use the source field to filter results.
Run is slower than expected	Lower maxItems or split large inputs into focused runs.
Too many retries or empty searches	Use more specific search terms. Empty or unavailable GETTR endpoints can still take time to confirm.
Missing media or engagement fields	GETTR may not expose those fields for every item. Check the raw GETTR page to confirm public availability.

Pricing guidance

This Actor is optimized for low-cost HTTP scraping and uses 128 MB memory by default. A pay-per-result pricing model is recommended so small tests stay inexpensive and larger successful runs scale with delivered value.

Recommended Apify monetization setup:

• Pricing model: Pay per event
• Event name: result
• Event trigger: one dataset item pushed
• Suggested public price: $0.00010 per result, or $0.10 per 1,000 results
• Platform usage: include normal platform usage in the per-result price rather than passing it through separately

Actual charges and availability depend on the pricing configured by the Actor owner in Apify Console.

FAQ

Can I scrape GETTR profiles?

Yes. Add GETTR profile URLs to startUrls or add usernames to usernames.

Can I scrape GETTR posts by URL?

Yes. Add one or more public GETTR post URLs to startUrls.

Can I search GETTR by keyword or hashtag?

Yes. Add keywords or hashtags to searchTerms. Result volume depends on what GETTR returns for the term.

Does this Actor need GETTR login cookies?

No. It collects public data and does not require a GETTR account.

Does it use a browser?

No. It uses public web API responses, which keeps memory and compute usage lower than browser automation for this use case.

How do I remove duplicate records?

The Actor deduplicates records inside each run by stable record type and GETTR ID. Downstream systems can also use type plus id as a unique key.

Is this an official GETTR product?

No. This is an independent Apify Actor for collecting public GETTR data.