Hoo.be Creator Scraper — Profiles, Links & Socials

Extract Hoo.be creator profiles, social links, outbound links, embeds and storefront data into clean structured JSON. Built for creator discovery, influencer research and creator economy apps.

No browser automation. One HTTP request per profile. No login, no proxy needed. Measured on 25 real profiles: 100% success, ~0.44 s and ~83 kB per profile, zero retries.

What does this Actor do?

Point it at hoo.be creator handles and it returns one clean record per creator: identity, bio, avatar, verification, every outbound link with a classified type, social accounts resolved into

{ platform, url, username }

It works as an unofficial data API over public Hoo.be profiles — usable from the Apify API, JavaScript/Python clients, schedules, webhooks, Make, Zapier and n8n.

What this Actor extracts

• Creator — creatorId, username, displayName, bio, profileUrl, avatarUrl, backgroundImageUrl, verified, customDomain
• Links — title, url, type, platform, position, thumbnailUrl, destinationDomain, isAdultContent
• Social profiles — platform, url, username (structured, not a URL dump)
• Products — price, productUrl, imageUrl, promoCode (rare — see Limitations)
• Embeds — variant, platform, contentId, embedUrl
• Tip jars — title and offered amounts
• Counts — linkCount, socialProfileCount, productCount, embedCount

Link types

SOCIAL · PRODUCT · SHOP · AFFILIATE · MUSIC · VIDEO · NEWSLETTER · COMMUNITY · DONATION · WEBSITE · OTHER

Classification is deterministic and unit-tested. Hoo.be labels each link's platform itself, so platform detection is read from the source, not guessed from the domain — domain matching is only a fallback when Hoo.be says other.

Social platforms detected

Instagram, TikTok, YouTube, X/Twitter, Twitch, Facebook, Snapchat, Threads, LinkedIn, Reddit, Pinterest, Discord, Telegram, Kick, Bluesky and more. Thirteen distinct platforms appeared across 25 test profiles.

Use cases

Influencer discovery

Create structured creator databases from Hoo.be profiles.

Creator economy analytics

Analyze how creators monetize — which stores, affiliate programs, newsletters and paid platforms they link to.

Agency CRM

Enrich creator records with public profile and social information.

Creator commerce

Track public products, prices and storefront links.

Social graph enrichment

Resolve one creator across every social platform they list.

Monitoring

Track profile, link and product changes over time.

Modes

Input

{ "mode": "PROFILE", "profiles": ["alixearle"] }

Handles, @handles and full URLs all work and are normalized automatically:

{
  "mode": "BATCH_PROFILES",
  "profiles": ["alixearle", "@perezhilton", "https://hoo.be/lydiaviolet"],
  "maxItems": 100
}

Output

{
  "creatorId": "67a92efe9debda9cc95ae103",
  "username": "perezhilton",
  "displayName": "Perez Hilton",
  "bio": "The original blogger…",
  "profileUrl": "https://hoo.be/perezhilton",
  "avatarUrl": "https://cdn.hoobe.media/…webp",
  "verified": true,
  "customDomain": null,
  "socialProfiles": [
    { "platform": "instagram", "url": "https://instagram.com/theperezhilton", "username": "theperezhilton" },
    { "platform": "tiktok", "url": "https://tiktok.com/@thatshowbizdude", "username": "thatshowbizdude" }
  ],
  "links": [
    { "linkId": "6a0cfb018ad436137862271e", "title": "LUCY NICOTINE",
      "url": "https://lucy.co/PEREZ", "type": "PRODUCT", "platform": null,
      "position": 3, "destinationDomain": "lucy.co", "isAdultContent": false }
  ],
  "products": [
    { "productId": "6a0cfb018ad436137862271e", "name": "LUCY NICOTINE",
      "price": 42, "currency": null, "productUrl": "https://lucy.co/PEREZ" }
  ],
  "embeds": [
    { "variant": "youtube-channel", "platform": "youtube",
      "contentId": "UC2xO_e0eSftVTvagxWxDQaQ", "embedUrl": "https://www.youtube.com/embed/…" }
  ],
  "linkCount": 9, "socialProfileCount": 9, "productCount": 1, "embedCount": 2,
  "email": null,
  "scrapedAt": "2026-08-23T20:51:34.170Z",
  "source": "hoo.be"
}

Download as JSON, CSV, Excel, XML or HTML. The Console ships two prepared views: Creators and Change events.

Monitoring & change detection

First run stores a baseline and reports nothing. Later runs compare and emit:

NEW_LINK · REMOVED_LINK · LINK_CHANGED · NEW_PRODUCT · PRODUCT_REMOVED · PRODUCT_PRICE_CHANGED · NEW_SOCIAL_PROFILE · SOCIAL_PROFILE_REMOVED · BIO_CHANGED · DISPLAY_NAME_CHANGED · AVATAR_CHANGED · VERIFIED_CHANGED

{
  "eventType": "PRODUCT_PRICE_CHANGED",
  "username": "somecreator",
  "subject": "Course bundle",
  "previousValue": 49,
  "currentValue": 39,
  "currency": null,
  "url": "https://example.com/course",
  "detectedAt": "2026-08-24T20:00:00.000Z",
  "profileUrl": "https://hoo.be/somecreator"
}

Two design guarantees, both tested: two runs over an unchanged profile produce zero events, and removals are never reported when the run only collected part of a profile (disabled sections or maxItems) — a missing link would otherwise look deleted when it simply wasn't fetched.

Set onlyChanges: true for scheduled monitoring: unchanged profiles produce no output and cost nothing beyond the run fee.

API usage

Replace <TOKEN> with your Apify API token.

curl

curl -X POST "https://api.apify.com/v2/acts/huykenny~hoobe-creator-scraper/run-sync-get-dataset-items?token=<TOKEN>" \
  -H 'Content-Type: application/json' \
  -d '{"mode":"PROFILE","profiles":["alixearle"]}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<TOKEN>' });
const run = await client.actor('huykenny/hoobe-creator-scraper').call({
    mode: 'BATCH_PROFILES',
    profiles: ['alixearle', 'perezhilton'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python

from apify_client import ApifyClient

client = ApifyClient("<TOKEN>")
run = client.actor("huykenny/hoobe-creator-scraper").call(
    run_input={"mode": "BATCH_PROFILES", "profiles": ["alixearle", "perezhilton"]}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items

Integrations

Standard Apify integrations apply: schedules, webhooks, Make, Zapier, n8n, Google Sheets/Drive, Slack, and the Apify MCP server (which exposes every Store Actor to AI agents — no separate MCP server needed for this Actor).

Pricing

Failed profiles, duplicate inputs and unchanged monitoring results are not charged.

Limitations

Stated plainly, because they are properties of Hoo.be, not of this Actor:

• Direct profile handles/URLs are the primary input. Hoo.be has no public search or full creator directory. DISCOVERY reads Hoo.be's public sitemap, which lists ~100 creators — a useful sample, not the whole platform.
• Products are rare. Only 1 of 65 tested profiles exposed a public price. The Actor extracts them when present, but most profiles have none.
• No currency on prices. Hoo.be publishes a price number without a currency, so currency is always null rather than a guess.
• No follower, revenue, sales or traffic figures. Hoo.be does not publish them publicly, so this Actor does not output or estimate them.
• No creator email. A Hoo.be contact block exposes only a button label, not an address. email is always null; no third-party enrichment is performed.
• Rate limits are real. Measured: 4 parallel requests with no delay produced HTTP 429 on 34 of 100 profiles. Defaults are deliberately conservative; lowering them may trigger throttling.
• Depends on Hoo.be's public page structure. If that changes, the Actor raises PAGE_STRUCTURE_CHANGED instead of quietly returning an empty profile.

Responsible use

This Actor requests only public profile pages (/{handle}) and Hoo.be's public sitemap.xml. It does not touch /api/ or link-redirect paths, both of which Hoo.be's robots.txt disallows, and it identifies itself honestly with its own User-Agent. No login, no CAPTCHA solving, no authentication bypass, no private or subscriber-only data, and no contact-detail guessing.

FAQ

Do I need a Hoo.be account? No. Only public pages are read.

Can I get every Hoo.be creator? No — Hoo.be publishes no full directory. Supply the handles you care about, or use DISCOVERY for the ~100 creators in the public sitemap.

Why is currency always null? Hoo.be doesn't publish one next to the price. Inventing "USD" would be a fabricated value.

Why no follower counts? Hoo.be doesn't expose them publicly.

Does one bad handle break the run? No. It becomes an error record in the dataset (not charged) and the run continues.

How do I get only changes? mode: MONITOR with onlyChanges: true.

Disclaimer

This Actor is not affiliated with or endorsed by Hoo.be. It extracts only publicly accessible data. Users are responsible for complying with applicable terms, privacy rules and laws.