GETTR Scraper: Profiles, Posts, Timelines & Search

Scrape public GETTR profiles, posts, user timelines, keyword search results, hashtags, media URLs, author metadata, and engagement metrics with a fast no-login API-first Apify Actor.

This GETTR scraper is built for OSINT research, social media monitoring, journalism, brand safety, influence analysis, competitor tracking, and data workflows that need structured GETTR data without running a browser or logging in. Use it as a GETTR profile scraper, GETTR post scraper, GETTR timeline scraper, GETTR search scraper, or GETTR API scraper for public data collection on Apify.

What This Actor Extracts

• GETTR user profiles by username or profile URL
• Public GETTR timelines and posts
• Individual GETTR posts from post URLs
• Keyword and hashtag search results
• Profile search fallback when post search is unavailable for a term
• Text, timestamps, language, hashtags, media URLs, video metadata, link previews, and engagement metrics
• Author details including username, display name, bio, website, profile image, follower counts, verification status, and badges

Why Use This GETTR Scraper

The Actor uses GETTR public web API endpoints with asynchronous HTTP requests. It avoids browser automation, so runs are lighter and more cost-effective than Selenium, Playwright, or Puppeteer-based scraping for public GETTR data.

It is designed for repeatable data extraction on Apify with cursor pagination, retry handling, normalized JSON output, and clean dataset exports.

Common Use Cases

• Monitor public GETTR posts mentioning brands, topics, people, or campaigns
• Build datasets for social media intelligence, NLP, entity extraction, or sentiment analysis
• Track public accounts, profile metadata, follower counts, and timeline activity
• Collect media URLs, video URLs, hashtags, and engagement metrics for content analysis
• Support OSINT, journalism, political research, and disinformation monitoring workflows
• Archive public GETTR posts and profile metadata for compliance or research

Input

Run the Actor from Apify Console, Apify API, schedules, webhooks, or integrations. Provide at least one of startUrls, usernames, or searchTerms.

Field	Type	Description
startUrls	array of strings	GETTR profile, post, or search URLs. You can also enter plain usernames.
usernames	array of strings	GETTR usernames to scrape. The @ prefix is optional.
searchTerms	array of strings	Keywords or hashtags to search on GETTR.
maxItems	integer	Maximum number of post/profile records to save across all inputs.

Example input:

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

Output

Results are stored in the default Apify Dataset as normalized JSON records. Each item has type: "post" or type: "user".

Post records can include:

• Post ID and canonical GETTR URL
• Text, language, created/updated timestamps, and post type
• Like, repost, reply, and view counts
• Hashtags, user tags, video tags, image URLs, video URLs, video duration, and video dimensions
• Link preview metadata
• Flat and nested author fields for easy exports

User records can include:

• Username, user ID, display name, bio, location, website, and language
• Follower/following counts and mirrored Twitter/X counts when GETTR provides them
• Verification status, badges, creator metadata, influence level, premium flag, and pinned post IDs
• Profile image and banner image URLs
• Created and updated timestamps

Example post item:

{
  "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,
  "postType": "vi_pst",
  "hashtags": ["news", "media"],
  "imageUrls": ["https://media.gettr.com/group/example/image.png"],
  "videoUrls": ["https://media.gettr.com/group/example/out.mp4"],
  "videoDurationSeconds": 57.52,
  "authorUsername": "exampleuser",
  "authorDisplayName": "Example User",
  "authorWebsite": "https://example.com",
  "authorFollowersCount": 3121,
  "authorIsVerified": false
}

Example user item:

{
  "type": "user",
  "source": "profile",
  "query": "support",
  "id": "support",
  "username": "support",
  "displayName": "Support & Help",
  "bio": "GETTR Support (Official Account)",
  "location": "New York, NY",
  "website": "https://support.gettr.com",
  "followersCount": 4105275,
  "followingCount": 1,
  "verificationStatus": "VERIFIED",
  "isVerified": true,
  "creatorBio": "Popular Creator",
  "profileImageUrl": "https://media.gettr.com/group/example/avatar.png",
  "bannerImageUrl": "https://media.gettr.com/group/example/banner.jpg"
}

Use With The Apify API

Install the Apify Python client:

$pip install apify-client

Run the Actor and read results from the default dataset:

from apify_client import ApifyClient

APIFY_TOKEN = "YOUR_APIFY_TOKEN"
ACTOR_ID = "thescrapelab/Apify-Gettr-Scraper"

client = ApifyClient(APIFY_TOKEN)

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

run = client.actor(ACTOR_ID).call(run_input=run_input)

if run is None:
    raise RuntimeError("Actor run failed")

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

You can also run the Actor from the Apify Console, export results as JSON, CSV, Excel, XML, RSS, or HTML, and connect the dataset to downstream systems through Apify integrations.

The Actor uses tuned internal request settings for a practical balance of speed, memory use, and reliability. For high-volume scraping, increase maxItems gradually.

Limitations

GETTR uses undocumented web API endpoints that can change over time. Search behavior may vary by term, region, or GETTR-side availability. The Actor includes retry and fallback logic, but endpoint changes can still affect result volume.

This Actor scrapes public GETTR data only. It does not access private content, deleted posts, logged-in-only content, or data that is not available through public GETTR pages/API responses.

Always use scraped data responsibly and comply with applicable laws, privacy rules, and platform terms.