# TikTok Followers & Following Scraper \[NO LOGIN] ✅ (`unseenuser/tiktok-followers-following-scraper`) Actor Bulk-scrape any TikTok user's followers and following lists. Get handles, names, follower counts, bios, regions. Built for lead gen, network mapping, influencer research, and ICP validation. No login, no cookies. Cheaper than every cookie-based alternative. - **URL**: https://apify.com/unseenuser/tiktok-followers-following-scraper.md - **Developed by:** [Unseen User](https://apify.com/unseenuser) (community) - **Categories:** Social media, Automation, Lead generation - **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 4 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing $5.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## TikTok Followers & Following Scraper - Network Mapping for Creators (No Login) > **Pull a TikTok creator's full follower list AND the accounts they follow. Built for network mapping, audience analysis, and lead generation. Bulk lists of named individuals - apply heightened compliance care.** > **Tier:** Tier 2 - Solid Niche (HIGHEST GDPR RISK - Launch Last) > **GDPR DISCLAIMER:** This Actor scrapes bulk personal data (handles, names, bios, follower counts). Use only in compliance with applicable privacy laws (GDPR, CCPA, Israeli Amendment 13, etc.). We provide the tool - compliance is the user responsibility. See who follows any creator. Map an influencer audience. Find lookalike prospects. Build creator-sourced lead lists at scale - all without a TikTok login. --- ### Quick reference | Property | Value | |---|---| | Public name | TikTok Followers & Following Scraper - Network Mapping for Creators (No Login) | | Apify slug | `UnseenUser/tiktok-followers-following-scraper` | | Short description | Pull a TikTok creator's full follower list AND the accounts they follow. Built for network mapping, audience analysis, and lead generation. Bulk lists of named individuals - apply heightened compliance care. | | Effective date | May 5, 2026 | | Keywords | `tiktok followers`, `tiktok following`, `network mapping`, `audience analysis`, `lead generation`, `competitor analysis` | --- ### Free plan limit Free Apify users get up to **50 results per run**. Paying users are not affected and receive results normally. This limit was set by the Actor developer, not by Apify. To remove it and receive unlimited results, upgrade to any paid Apify plan: https://apify.com/pricing When a free plan run hits the cap, the Actor finishes successfully (status `SUCCEEDED`) and the run's status message explains what happened. No error is raised, so the first 50 results are fully usable as normal. --- ## Part 1: Public-facing overview ### Why this Actor Combined-endpoint atomic Actor: input a TikTok handle (or many), get back full lists of followers AND who they follow. Each user record includes handle, display name, bio, and follower / following counts. This is bulk personal data - the highest GDPR exposure of any TikTok Actor in this suite. Apply data minimization, document a lawful basis, honor data subject rights, and assume regulator scrutiny. ### Use cases - **Network mapping** - see who follows whom in your industry - **Audience analysis** - analyze the composition of a creator's audience (research only) - **Influencer-overlap analysis** - find creators whose audiences overlap for cross-promotion - **Competitor analysis** - see who follows competing brand accounts (with extreme care) - **Academic research** - social network analysis on TikTok structures - **Lead generation** - identify accounts following a topic-leader for outreach (with strict compliance) - **Talent scouting** - find rising creators that established creators in your niche already follow - **Trend forensics** - retrospectively check who was following a creator before a viral moment ### Workflow 1. Pick a competitor or aspirational creator in your niche. 2. Run this Actor with their handle (or pass several handles for a bulk run). 3. Get the follower list, the following list, or both. 4. Enrich the resulting profiles via the TikTok User Search Actor for outreach-ready records. 5. Cross-reference with the TikTok Audience Geography Actor to see where the audience actually lives. ### How this compares | Option | Price tier | TikTok account ban risk | Bulk scale | GDPR position | |---|---|---|---|---| | **This Actor** | Pay-per-event on Apify | None (no login required) | Up to 50,000 users per run | User is data controller; Actor is software vendor | | Clockworks-style add-ons (approx $4 / 1k) | Per-record | None | Medium | Opaque - varies by vendor | | Cookie-based scrapers | Free / DIY | High (your account can get banned) | Low / brittle | Often non-compliant; relies on a logged-in session | | Manual export from TikTok | Free | None (no automation) | Tiny (a few hundred at a time) | You are still the data controller | ### Quick start 1. Click **Try for free** on this Actor's page 2. Enter one TikTok handle (without the @) in `handle`, or many in `handles` 3. Run the Actor 4. Download results as JSON, CSV, or XLSX, or pull via the Apify API ### Inputs overview | Input | Type | Required | Description | Example / allowed values | |---|---|---|---|---| | `handles` | string[] | Yes | One or more TikTok handles and/or full profile URLs, one per line. Each entry can be a bare handle, an `@handle`, or a `https://www.tiktok.com/@handle` URL. Multiple entries are processed sequentially with per-handle error isolation. | `["stoolpresidente", "https://www.tiktok.com/@barstoolsports"]` | | `get_followers` | boolean | No | Include followers list. Default `true`. | true | | `get_following` | boolean | No | Include following list. Default `true`. | true | | `max_users_total` | integer | No | Hard cap on total users returned per run (across all handles). Default 5000, max 50000. | 5000 | | `max_pages_followers` | integer | No | Max pages of followers to fetch, per handle. Default 50. | 50 | | `max_pages_following` | integer | No | Max pages of following to fetch, per handle. Default 50. | 50 | #### Handles and URLs Each `handles` entry can be a bare handle (`stoolpresidente`), an `@handle` (`@stoolpresidente`), or a full TikTok profile URL (`https://www.tiktok.com/@stoolpresidente`). The Actor normalizes everything to a clean handle internally - paste whichever form is easier for your workflow. #### Bulk mode Add several entries to `handles` to scrape multiple creators in one run. Each entry is processed sequentially. If one fails (private account, deleted, network blip), the Actor records the failure as an error row and continues with the rest - one bad entry never crashes the whole run. The `max_users_total` cap applies to the run as a whole, while `max_pages_followers` / `max_pages_following` apply per handle. #### Performance note When a numeric `user_id` is available internally, the Actor uses it transparently for the followers lookup because it is significantly faster than handle-based lookup. The following lookup only supports handle. You always supply a handle - the optimization is invisible to you. ### Sample output ```json [ { "list_type": "followers", "target_handle": "stoolpresidente", "uid": "6614519312189829121", "unique_id": "marketing_mike", "nickname": "Marketing Mike", "follower_count": 14210, "following_count": 312, "signature": "B2B SaaS growth. DMs open for collabs.", "avatar_url": "https://p16-sign.tiktokcdn-us.com/.../avatar.jpeg", "_metadata": { "page": 1, "fetched_at": "2026-05-05T12:00:00.000Z", "input_identifier": "stoolpresidente" } }, { "list_type": "followers", "target_handle": "stoolpresidente", "uid": "7011004567890123456", "unique_id": "sportsfan_anna", "nickname": "Anna", "follower_count": 412, "following_count": 998, "signature": "Boston sports + dogs", "avatar_url": "https://p16-sign.tiktokcdn-us.com/.../avatar2.jpeg", "_metadata": { "page": 1, "fetched_at": "2026-05-05T12:00:00.000Z", "input_identifier": "stoolpresidente" } }, { "list_type": "followers", "target_handle": "stoolpresidente", "uid": "7100020003000400500", "unique_id": "creator_jane", "nickname": "Jane | Content", "follower_count": 92800, "following_count": 145, "signature": "Short-form video studio. Brand inquiries: link in bio.", "avatar_url": "https://p16-sign.tiktokcdn-us.com/.../avatar3.jpeg", "_metadata": { "page": 1, "fetched_at": "2026-05-05T12:00:00.000Z", "input_identifier": "stoolpresidente" } }, { "list_type": "following", "target_handle": "stoolpresidente", "uid": "6720000001112223334", "unique_id": "espn", "nickname": "ESPN", "follower_count": 18900000, "following_count": 220, "signature": "Official ESPN account.", "avatar_url": "https://p16-sign.tiktokcdn-us.com/.../avatar4.jpeg", "_metadata": { "page": 1, "fetched_at": "2026-05-05T12:00:00.000Z", "input_identifier": "stoolpresidente" } }, { "list_type": "following", "target_handle": "stoolpresidente", "uid": "6730000002223334445", "unique_id": "barstoolsports", "nickname": "Barstool Sports", "follower_count": 15400000, "following_count": 38, "signature": "Comedy, sports, and the occasional take.", "avatar_url": "https://p16-sign.tiktokcdn-us.com/.../avatar5.jpeg", "_metadata": { "page": 1, "fetched_at": "2026-05-05T12:00:00.000Z", "input_identifier": "stoolpresidente" } } ] ```` Failed page fetches and failed bulk-mode handles are emitted as rows with an `error` field so the run never crashes on partial failures. ### Output fields | Field | Description | |---|---| | `list_type` | `followers`, `following`, or `error` | | `target_handle` | The handle being scraped (echoes back which input the row belongs to) | | `uid` | TikTok internal numeric user ID | | `unique_id` | TikTok handle (without @) | | `nickname` | Display name | | `follower_count` | This user's follower count | | `following_count` | How many accounts this user follows | | `signature` | Bio text | | `avatar_url` | Profile picture URL | | `_metadata` | `{ page, fetched_at, input_identifier }` for traceability | | `error` | Present only on error rows; human-readable failure description | ### Pricing Pay-per-event model on Apify. See exact per-event pricing on the Actor's Apify page. ### FAQ **Q: Is this legal?** A: Your downstream use of the returned data is your responsibility - see the full Terms of Service and the Actor-Specific Addendum below for details. **Q: Do I need any third-party account?** A: No. UnseenUser holds the underlying credentials. You only need an Apify account. **Q: What about TikTok's anti-scraping enforcement?** A: TikTok's Terms restrict automated extraction. Your downstream use must comply with TikTok's Terms. **Q: What if TikTok sends a cease-and-desist?** A: Notify UnseenUser within 48 hours via the Apify profile contact form (apify.com/UnseenUser) and cease using this Actor immediately. **Q: Can I use this data to train AI?** A: No. TikTok's Terms explicitly prohibit AI training on TikTok data, and creators retain copyright in their content. **Q: What about minors?** A: TikTok has many under-18 users. This Actor's Terms strictly prohibit using data of users you know or suspect are minors. See Part 4 (Actor-Specific Addendum) below. **Q: What if the target user has 10M followers?** A: The Actor still works, but you should plan around `max_users_total` (hard maximum is 50,000 per run). To pull a larger network, run the Actor in multiple sessions with paging. **Q: What is the maximum per run?** A: 50,000 users per run, 5,000 by default. Free plan: 50 items per run. **Q: Are there rate limits?** A: The Actor performs internal retries with exponential backoff on transient failures, so most runs need no tuning. **Q: Handle vs user\_id, which should I use?** A: This Actor only accepts handles as input. The followers lookup is faster internally when a numeric `user_id` is available, and the Actor uses it transparently when possible. The following lookup only supports handle. **Q: Can I run this on multiple creators at once?** A: Yes. Pass them all in `handles`. The Actor processes them sequentially with isolated error handling - one failing handle does not stop the others. **Q: What if the target profile is private?** A: Private profiles do not expose follower / following lists publicly. The Actor will record the failure as an error row and move on. ### Technical details - Output: streamed via the Apify dataset - Formats: JSON, CSV, XLSX, or via the Apify API - Retries: 3 with exponential backoff (1s, 2s, 4s) on transient HTTP failures - User agent: `OpusScale-Apify/1.0` - Bulk mode: per-handle error isolation, sequential processing - Live view: minimal HTTP status page reachable via the Actor's public URL while a run is active ### Related scrapers Build the complete TikTok lead-gen pipeline: - [TikTok Audience Geography](https://apify.com/unseenuser/TikTok-Audience-Geography) - see WHERE the followers live, not just who - [TikTok Trends Scraper](https://apify.com/unseenuser/TikTok-Search-Scraper) - find creators with the right audience - [LinkedIn Profile Scraper + Email Enrichment](https://apify.com/unseenuser/LinkedIn-Profile) - cross-platform enrichment [See all scrapers by unseenuser](https://apify.com/unseenuser) ### Target keywords tiktok followers scraper, tiktok following scraper, scrape tiktok followers, tiktok user list, tiktok lead gen, follower list extraction, tiktok network mapping, bulk tiktok scraper *** ## Part 3: Apify Actor - Terms of Service **Version:** 4.0 **Effective Date:** May 5, 2026 *** ### 0. ACCEPTANCE BY USE - IMPORTANT **Read this section first.** These Terms of Service ("Terms") form a binding legal agreement between you ("User," "you," "your") and UnseenUser, the Publisher of this Apify actor ("UnseenUser," "the Publisher," "we," "us," "our"). #### 0.1 How You Accept These Terms You accept these Terms by **any of the following actions**, each of which constitutes a clear, affirmative act of acceptance: - (a) **Running the Actor** - Initiating any execution of the Actor on the Apify platform - (b) **Using any output** returned by the Actor for any purpose - (c) **Continuing to access** the Actor's listing or documentation after these Terms are visible #### 0.2 Continuing Acceptance Each time you run the Actor or use its outputs, you reaffirm your acceptance of the then-current Terms. If you do not agree to these Terms or any subsequent update, you must stop using the Actor immediately. #### 0.3 No Anonymous Acceptance You cannot disclaim acceptance by: - Failing to read these Terms before running the Actor - Running the Actor through automated systems - Sharing your Apify account with others who may not have read these Terms By the act of running the Actor on Apify, you bind yourself, your organization (if applicable), and any individuals or systems acting on your behalf or under your authority. #### 0.4 If You Do Not Accept **If you do not agree to these Terms, you must not run the Actor.** No use is authorized without acceptance. *** ### PREAMBLE - UNDERSTANDING THE ARCHITECTURE Before using the Actor, please understand the technical architecture of the service: #### The Data Flow ``` You (User) -> Apify Platform -> Actor (software) -> Third-Party API -> Source Platform | You (User) <- Apify Platform <- Actor (software) <- Third-Party API ``` #### What Each Party Does - **You (the User):** Run the Actor on the Apify platform with input parameters you choose - **Apify:** Operates the cloud infrastructure that hosts and executes Actors. Apify is a Czech-incorporated company (Apify Technologies s.r.o.) governed by its own Terms of Service. - **The Publisher (us):** Publishes software code (the Actor) on Apify's platform. The Actor is a thin wrapper that translates your input into requests to a third-party API and returns the API's responses to you. **The Publisher does not operate scraping infrastructure. The Publisher does not store or retain data returned by the Actor. The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through.** - **Third-Party API Provider:** Independent third-party company that operates scraping infrastructure and returns data from source platforms. - **Source Platform:** LinkedIn, TikTok, YouTube, Reddit, Linktree, etc. These are the platforms whose publicly visible data is accessed by the Third-Party API Providers. #### Why This Matters Your relationship with the Publisher is that of a **software user** to a **software vendor**. The Publisher has the responsibilities of a software vendor (functional code, accurate documentation) and the limits of one (the Publisher is not responsible for how you use the data you obtain). *** These Terms operate alongside but do not replace: - Apify's Terms of Service and Acceptable Use Policy (governing your relationship with Apify) - Third-Party API Provider Terms of Service (governing the underlying data infrastructure) - Source Platform terms (LinkedIn, TikTok, etc.) governing the public data accessed - Applicable law in your jurisdiction and the jurisdictions of data subjects These Terms incorporate the actor-specific addendum published in each Actor's individual listing ("Addendum"). In the event of a conflict, the more restrictive provision applies. *** ### 1. NATURE OF THE SERVICE #### 1.1 What the Actor Is The Actor is a software program published on the Apify platform. Each Actor: - (a) Accepts structured input from you on the Apify platform - (b) Translates that input into HTTP requests to a third-party API - (c) Receives HTTP responses from that third-party API - (d) Returns the response data to you in a structured format on the Apify platform The Actor's source code is hosted on Apify's infrastructure. The Actor runs in Apify's cloud, not on the Publisher's servers. The Publisher operates no servers running the Actor. #### 1.2 What the Actor Is Not The Actor is **not**: - (a) A scraping tool - the Publisher does not operate scraping infrastructure, proxies, headless browsers, or fake accounts - (b) A direct connection to any source platform - connections to source platforms are made by the third-party API provider - (c) A data storage or data retention service - the Publisher does not maintain a database of any data the Actor returns - (d) A licensed access channel to LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta, Linktree, or any other source platform - (e) Affiliated with, endorsed by, sponsored by, or authorized by any source platform #### 1.3 The Publisher's Limited Role The Publisher's role is limited to: - (a) Designing and writing the Actor's source code - (b) Publishing the Actor on the Apify Store - (c) Maintaining the Actor (updating it when API providers change schemas) - (d) Providing documentation and customer support via Apify's contact mechanism The Publisher is a software vendor, similar to a developer who publishes an app on the Apple App Store or Google Play Store. The Publisher is not a data provider, data broker, data processor, or data controller for purposes of GDPR, CCPA, Israel's Privacy Protection Law, or equivalent. #### 1.4 The Third-Party API Provider's Role The third-party API provider is an independent company. They: - (a) Operate the actual data scraping infrastructure - (b) Maintain relationships with source platforms (or accept the operational risk of accessing public data without such relationships) - (c) Provide their own Terms of Service governing their operations - (d) Are responsible for compliance obligations relating to the data collection itself The Publisher is a customer of the provider. The Publisher is not their agent, partner, or representative. *** ### 2. WHO MAY USE THE ACTOR #### 2.1 Eligibility You may use the Actor only if: - (a) You are at least 18 years old or the age of majority in your jurisdiction - (b) You have legal capacity to enter into binding contracts - (c) You are not located in or resident of a country subject to comprehensive sanctions by the United States, European Union, United Kingdom, or Israel - (d) You are not on any prohibited persons list #### 2.2 User Representations By using any Actor, you represent and warrant that: - (a) **Truthful identity:** Information you provide about your identity and intended use is accurate - (b) **Lawful intent:** Your intended use complies with applicable law in your jurisdiction - (c) **Source platform compliance:** You will independently comply with the Terms of Service of any source platform whose data you obtain through the Actor - (d) **Data subject rights:** Where Actor outputs include personal data, you will respect data subject rights under applicable law - (e) **No prohibited use:** You will not use the Actor for any of the purposes prohibited in Section 4 These representations are continuous - they must remain true throughout your use. *** ### 3. PERMITTED USES The Actor may be used for any lawful purpose, including: - Market research and competitive analysis - Academic research - Journalism and investigative reporting - Internal business intelligence - Brand monitoring - Recruitment research where consistent with applicable employment law - Building products that further process publicly available information lawfully Specific permitted uses for this Actor are described in the Addendum below. *** ### 4. PROHIBITED USES You may not use the Actor for any of the following: #### 4.1 Illegal Activity Activity illegal under the law of your jurisdiction, the User's jurisdiction, or the jurisdiction of any data subjects. #### 4.2 Harassment, Stalking, and Personal Targeting - Compiling profiles for harassment, stalking, or doxxing - Tracking individuals' movements or activities without their knowledge - Building profiles of journalists, activists, dissidents, or vulnerable populations for retaliatory purposes #### 4.3 Discrimination - Using outputs for discriminatory employment, lending, housing, or insurance decisions based on protected characteristics - Building lists for discriminatory purposes #### 4.4 Spam and Unsolicited Commercial Communication - Sending unsolicited marketing in violation of CAN-SPAM, CASL, GDPR, PECR, Israeli Anti-Spam Law, or equivalent laws - Building "lead lists" from scraped contacts without proper consent infrastructure - Reselling contact data for spam purposes #### 4.5 Fraud and Deception - Identity theft or impersonation - Generation of fake reviews, testimonials, or coordinated inauthentic behavior - Election interference or political disinformation - Securities fraud #### 4.6 Source Platform Abuse - Using outputs to circumvent technical protection measures of source platforms - Creating fake accounts on source platforms based on Actor outputs - Vote manipulation, engagement manipulation, or platform algorithm gaming - Building services that competitively substitute for source platforms #### 4.7 Reselling the Actor's Service - Reselling raw Actor outputs as your own data product or scraping-as-a-service - Sharing your Apify credentials to provide third parties indirect access - Building competing API services using Actor outputs #### 4.8 AI Training Without Authorization - Using Actor outputs as training data for commercial AI/ML models without separate licensing authority from the source platform #### 4.9 Sensitive Targeting - Specifically targeting or profiling based on health conditions, sexual orientation, religious beliefs, political opinions, or other sensitive characteristics - Targeting children under 16 (or local age of consent for data processing) #### 4.10 Privacy Law Violations - Processing personal data of EU/UK/California/Israeli residents without complying with applicable privacy law - Failing to honor data subject access, deletion, or objection requests - Processing data for purposes incompatible with its publication context *** ### 5. SOURCE PLATFORM TERMS - YOUR RESPONSIBILITY #### 5.1 Acknowledgment The Actor accesses publicly visible data on third-party platforms ("Source Platforms") through the third-party API provider. Source Platforms include LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta/Facebook, Linktree, Komi, Pillar, Linkbio, Linkme, and Amazon. #### 5.2 Your Sole Responsibility You acknowledge: - (a) **You are solely responsible for ensuring your downstream use of data obtained through the Actor complies with the Source Platform's Terms of Service** - (b) The Publisher makes no representation that any specific use is permitted under any Source Platform's terms - (c) The third-party API provider, not the Publisher, bears responsibility for the lawfulness of the data collection itself - (d) You should review Source Platform terms before commercial use: - LinkedIn: https://www.linkedin.com/legal/user-agreement - TikTok: https://www.tiktok.com/legal/page/global/terms-of-service/en - YouTube: https://www.youtube.com/static?template=terms - X: https://twitter.com/en/tos - Reddit: https://www.redditinc.com/policies/user-agreement - Meta: https://www.facebook.com/legal/terms - Linktree: https://linktr.ee/s/terms/ #### 5.3 Cease-and-Desist Compliance If you receive a cease-and-desist letter or other legal demand from a Source Platform regarding your use of Actor outputs, you must: - (a) Cease the contested use immediately - (b) Notify UnseenUser within 48 hours via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) - (c) Cooperate with the Publisher as needed to mitigate - (d) Not assert against the Publisher any claim arising from your inability to use the Actor for that Source Platform *** ### 6. DATA PROTECTION - REFLECTING ACTUAL ARCHITECTURE #### 6.1 Roles Under Privacy Law For purposes of GDPR, UK GDPR, CCPA, Israel's Privacy Protection Law (PPL) including Amendment 13, and equivalents: - **You (the User) are the Data Controller** of any personal data you obtain through the Actor and subsequently process for your own purposes - **The third-party API provider** is the entity that collects data from source platforms - they bear the responsibilities of data processors or controllers (depending on context) for the collection itself - **The Publisher acts solely as a software vendor**, not as a data controller or processor, because the Publisher does not store, retain, or substantively process personal data - the Actor merely passes API responses through #### 6.2 No Data Retention by the Publisher The Publisher confirms: - (a) The Publisher does not maintain a database of personal data obtained through the Actor - (b) The Actor passes data from the third-party API directly to you on the Apify platform - data does not flow through the Publisher's infrastructure - (c) Apify's standard execution and operational logging may include limited information about Actor runs (input parameters, run duration, data volume) - this is governed by Apify's own privacy practices - (d) The Publisher does not access, view, or analyze your Actor outputs except as needed for technical support if you specifically share them with the Publisher #### 6.3 Your Obligations as Data Controller Where your use of the Actor involves processing personal data, you are responsible for: - (a) Establishing a lawful basis for your processing (consent, legitimate interest with documented balancing test, contract, etc.) - (b) Providing transparent notice to data subjects as required by applicable law - (c) Honoring data subject access, rectification, erasure, restriction, and portability requests - (d) Implementing appropriate security measures - (e) Conducting Data Protection Impact Assessments where required - (f) Appointing a Data Protection Officer if your operations require one - (g) Registering databases with applicable supervisory authorities - (h) Honoring opt-out requests for direct marketing - (i) Cross-border transfer safeguards where data crosses borders #### 6.4 Israel's Amendment 13 - User Compliance If your use of the Actor involves Israeli residents' personal data, you must comply with the Privacy Protection Law as amended (Amendment 13, effective August 14, 2025). These obligations are yours as the data controller, not the Publisher's as the software vendor. #### 6.5 Sensitive Data Targeting Restrictions You will not use the Actor to specifically target, profile, or build datasets focused on: - Health or medical conditions - Religious beliefs - Political opinions - Sexual orientation or gender identity - Genetic or biometric data - Criminal history - Children under 16 *** ### 7. INTELLECTUAL PROPERTY #### 7.1 Actor Code The Actor's source code, schemas, documentation, and branding are owned by the Publisher. You receive a limited, non-exclusive, non-transferable, revocable license to use the Actor for permitted purposes during your active subscription/run with Apify. #### 7.2 Output Data The Publisher claims no ownership over the public data the Actor returns. Source Platforms may have copyright, database rights, or other rights in their data; data subjects may have copyright in user-generated content. Your use of output data must respect these rights independently. #### 7.3 Restrictions You may not reverse engineer, decompile, or reuse the Actor's code in a competing actor. #### 7.4 Feedback Feedback you provide may be used by the Publisher to improve products without compensation to you. *** ### 8. PRICING AND PAYMENT #### 8.1 Apify Platform Billing Pricing is administered through Apify's pricing models. Apify processes all payments. Apify's payment terms govern refunds and disputes. #### 8.2 Pricing Changes The Publisher may change Actor pricing with at least 14 days' notice via the Actor's Apify listing. #### 8.3 No Refunds for Misuse If your access is suspended or terminated for breach of these Terms, you forfeit any unused balance and are not entitled to refunds. *** ### 9. SERVICE AVAILABILITY AND CHANGES #### 9.1 No Uptime Guarantee The Actor depends on: - (a) The Apify platform - (b) The underlying third-party API provider - (c) Source Platforms' continued public accessibility Any of these may change behavior, restrict access, or become unavailable without notice. The Publisher makes no uptime guarantees. #### 9.2 Service Discontinuation The Publisher may discontinue any Actor at any time. Reasonable notice will be provided when feasible. *** ### 10. DISCLAIMERS #### 10.1 "AS IS" Service THE ACTOR IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR PURPOSE, NON-INFRINGEMENT, OR ACCURACY OF DATA. #### 10.2 No Representation of Lawfulness The Publisher makes no representation that your specific use of the Actor or the data it returns is lawful in your jurisdiction or under any Source Platform's terms. The burden of determining lawfulness for your use case is yours. #### 10.3 No Endorsement of Source Content Content returned by the Actor was created by third parties. The Publisher does not endorse, verify, or take responsibility for it. *** ### 11. LIMITATION OF LIABILITY #### 11.1 Aggregate Liability Cap TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE PUBLISHER FOR ALL CLAIMS RELATING TO THE ACTOR EXCEED THE GREATER OF: - (a) ONE HUNDRED U.S. DOLLARS (US $100), OR - (b) THE AMOUNTS YOU PAID THROUGH APIFY FOR USE OF THE ACTOR IN THE THREE (3) MONTHS IMMEDIATELY PRECEDING THE EVENT #### 11.2 Excluded Damages THE PUBLISHER IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, OR DATA, EVEN IF ADVISED OF THE POSSIBILITY. #### 11.3 Time Limit Any claim must be brought within one (1) year of the event. *** ### 12. INDEMNIFICATION #### 12.1 Your Indemnification of the Publisher You agree to defend, indemnify, and hold harmless the Publisher from any: - Claims arising from your use of the Actor - Claims arising from your violation of these Terms - Claims arising from your violation of any law (including privacy law) - Claims arising from your violation of any Source Platform's Terms of Service - Claims arising from your processing of personal data obtained through the Actor - Reasonable attorneys' fees and costs of defending such claims #### 12.2 Defense The Publisher may assume defense at your expense. You will cooperate with the Publisher's defense. #### 12.3 Scope The indemnification covers reasonable, foreseeable third-party claims arising from your use. It does not extend to: - Claims arising from the Publisher's gross negligence or willful misconduct - Claims regarding the Actor's source code itself (those are the Publisher's responsibility) - Claims regarding the third-party API provider's data collection (those are their responsibility) *** ### 13. SUSPENSION AND TERMINATION #### 13.1 Termination by the Publisher The Publisher may terminate your access for material breach, illegal use, breach of warranty, or upon credible legal demand. #### 13.2 Effects of Termination Your license ends, you must cease use, and applicable provisions survive. #### 13.3 Termination by You You may stop using the Actor at any time on Apify. *** ### 14. DISPUTE RESOLUTION #### 14.1 Informal Resolution First Send a detailed written description of the dispute via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) and wait 60 days for resolution attempt before any formal claim. #### 14.2 Governing Law These Terms are governed by the substantive laws of the State of Israel, without regard to conflict of law principles. #### 14.3 Exclusive Jurisdiction Any dispute shall be brought exclusively in the competent civil courts of Tel Aviv-Jaffa, Israel. #### 14.4 No Class Actions You agree to bring claims only in your individual capacity. #### 14.5 Attorneys' Fees The prevailing party recovers reasonable attorneys' fees. *** ### 15. MISCELLANEOUS #### 15.1 Entire Agreement These Terms (with Addendum and incorporated documents) are the entire agreement. #### 15.2 Severability Unenforceable provisions are reformed to the minimum extent or severed. #### 15.3 Assignment You may not assign without the Publisher's consent. The Publisher may assign to affiliates, successors, or acquirers. #### 15.4 Force Majeure Neither party is liable for failure due to events beyond reasonable control, including changes by Source Platforms or the third-party API provider, or actions by Apify. #### 15.5 Third-Party Beneficiaries Apify and the third-party API provider are intended third-party beneficiaries of Sections 4 (Prohibited Uses), 5 (Source Platform Compliance), and 12 (Indemnification). #### 15.6 Survival Sections 0 (Acceptance), 4, 5, 6, 7, 10, 11, 12, 14, and 15 survive termination. #### 15.7 Language English controls. Translations are for convenience only. #### 15.8 Publisher Identification for Legal Process The Publisher operates on the Apify platform under the username **UnseenUser** (apify.com/UnseenUser). The Publisher is a registered legal entity. Upon receipt of valid legal process (subpoena, court order, or equivalent) directed through Apify's official channels, the Publisher's full legal identity may be disclosed as required by law. This Section ensures that you have a valid path to legal recourse if needed. *** ### 16. ACKNOWLEDGMENT By using any Actor, you acknowledge that: - (a) You have read these Terms - (b) You understand the architecture: you are using software (the Actor) on Apify's platform that calls a third-party API - (c) You accept responsibility for your use, including for compliance with Source Platform terms - (d) Your indemnification obligations cover third-party claims arising from your use - (e) Disputes are resolved in Israeli courts - (f) The Publisher's identity, while not publicly disclosed in this listing, can be obtained through valid legal process via Apify For questions, use UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) before running the Actor. *** ### APPENDIX - Document Version History | Version | Date | Summary | |---------|------|---------| | 1.0 | May 5, 2026 | Initial publication | | 2.0 | May 5, 2026 | Hardened (over-broad - treated User as data broker) | | 3.0 | May 5, 2026 | Architecturally accurate - Publisher as software vendor | | 4.0 | May 5, 2026 | Anonymous Publisher. All personally identifying information removed. Acceptance-by-Use mechanism formalized. | *** *These Terms reflect best practices for anonymous Apify actor publishing as of May 2026. Not a substitute for legal advice. Consult qualified Israeli commercial counsel before deploying.* *** ## Part 4: Actor-Specific Terms of Service Addendum - TikTok Followers & Following Scraper This addendum supplements the Master Terms of Service V4.0 above. By running this Actor, you accept both the Master ToS and this addendum. #### A. Architectural Disclosure This Actor is a software wrapper. It accepts your input parameters, calls the underlying followers and following endpoints, and returns the response data to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. The data flows from the third-party API through Apify's runtime directly to you. #### B. Nature of Data Returned This Actor returns two lists per run: 1. **Followers** - every user following the target creator 2. **Following** - every user the target creator follows Each user includes `uid`, `unique_id` (@handle), `nickname`, `follower_count`, `following_count`, `signature` / bio, and avatar URLs. Where the Actor's output includes individual people's names, photos, contact details, or content authored by them, that data constitutes **personal data** subject to GDPR, CCPA, Israeli Privacy Protection Law (including Amendment 13), and equivalent privacy laws in your downstream processing - but **only in your hands as the data controller**, not in UnseenUser's hands as the software vendor. #### C. Permitted Use Cases You may use this Actor for the following purposes (non-exhaustive list): - **Network mapping** - see who follows whom in your industry - **Audience analysis** - analyze the composition of a creator's audience (research only) - **Influencer-overlap analysis** - find creators whose audiences overlap for cross-promotion - **Competitor analysis** - see who follows competing brand accounts (with extreme care) - **Academic research** - social network analysis on TikTok structures - **Lead generation** - identify accounts following a topic-leader for outreach (with strict compliance) #### D. Specifically Prohibited Uses In addition to Master ToS Section 4 prohibitions, you may NOT: - Mass cold-DM every follower in the returned list - even with personalization, this is spam under most regimes - Sell follower lists as a product - clearly data broker activity, regulatory red line - Aggregate follower lists across many target accounts to build a comprehensive "TikTok user database" - Use follower lists to target individuals for harassment, brigading, or political pressure - Use follower data to identify minors and add them to commercial outreach lists - Build "who-follows-whom" surveillance tools tracking specific individuals over time - Resell follower data as a substitute for TikTok's official analytics tools - Use follower lists to identify and target users with content that violates their content preferences (radicalization, deceptive marketing) #### E. Platform Terms of Service Considerations TikTok's Terms of Service prohibit automated extraction. Bulk follower-list extraction is the highest-sensitivity TikTok scraping operation. If TikTok or a regulator issues a cease-and-desist, notify UnseenUser within 48 hours via the Apify profile contact form (apify.com/UnseenUser) and cease use IMMEDIATELY. #### F. HIGHEST GDPR EXPOSURE OF ANY ACTOR IN THIS SUITE This Actor returns **bulk lists of named individuals' personal data**. This is the highest-risk category under: - **GDPR** - Article 6 (lawful basis), Article 14 (transparency to data subjects you did not collect from), Article 9 (if any user's profile reveals special categories), Article 22 (automated decisions) - **Israeli Privacy Protection Law Amendment 13** - bulk personal data processing, statutory damages of NIS 10,000 per data subject without proof of harm - **CCPA / CDPA / etc.** - opt-out rights, data sale prohibitions, data broker registration requirements - **California Delete Act** - effective 2026, specifically targets follower-list-style data aggregation If your downstream use cannot survive regulatory scrutiny under one of these frameworks, **do not use this Actor.** #### G. Lawful Basis Requirements - Specifically For GDPR-covered processing, you MUST: 1. **Document lawful basis** - typically Article 6(1)(f) legitimate interest with a completed Legitimate Interest Assessment (LIA) 2. **Complete the LIA balancing test** - ask: would the average TikTok user reasonably expect their follower-list inclusion to enable commercial outreach? Recent EU DPA decisions increasingly say NO 3. **Issue Article 14 transparency notices** - when you collect personal data from a source other than the data subject, you must inform them within a reasonable period (1 month or first contact) 4. **Honor Article 21 right to object** - for direct marketing, this is ABSOLUTE - not subject to a balancing test 5. **Implement data minimization** - store only what you actually need (e.g., signal "follows X" rather than full user records) 6. **Set retention limits** - do not retain follower lists indefinitely #### H. The Data Broker Question A follower list across MANY accounts IS a data broker asset. California's data broker registration requirements (effective 2024+) apply if you: - Collect personal data from a source that is not the consumer - Sell or share that data If your business model includes selling follower lists or insights derived from them, you may need to register as a data broker in California (and possibly other states). Consult an attorney. #### I. Minor Protection - CRITICAL Followers and following lists may contain minors. You MUST: - Filter known minors from your downstream use - Treat ambiguous-age users as minors by default for outreach purposes - Do not aggregate minor data across multiple accounts (COPPA escalation risk) - Delete data you discover relates to minors without parental consent #### J. Algorithmic Discrimination Using follower lists to make decisions about individuals (employment, lending, marketing eligibility) may trigger: - **GDPR Article 22** - right to human review of automated decisions - **FCRA** (US) - consumer reporting obligations if used for credit/employment - **Title VII** (US) - disparate impact analysis if used in hiring - **EU AI Act** - high-risk AI categorization for certain uses Do not build algorithmic decision systems on follower-list data without legal review. #### K. Network Surveillance - Prohibited Pattern Building a database that tracks specific individuals' follower / following relationships over time is SURVEILLANCE. This is prohibited even if technically permitted by the platform. Patterns to avoid: - "Pull follower list of @target\_account weekly to detect when @specific\_individual follows them" - "Build a graph database of follower relationships of 1000 named individuals" - "Track when @rival\_creator's followers change over the last 12 months" These patterns: - Violate the privacy interests of the people being tracked - Create surveillance datasets that are catnip to regulators and bad actors - Cross clearly into data broker territory #### L. Endpoint Parameter Difference Note an asymmetry in the underlying source: - **Followers** lookup accepts EITHER `handle` OR `user_id` (user\_id is faster) - **Following** lookup accepts ONLY `handle` (no user\_id support) The Actor handles this transparently - you only provide a handle. #### M. Aggregation Cap - Built Into Actor To reduce regulatory exposure, this Actor implements a hard cap on results per run (default 5,000 users; max 50,000). To get more, you must run the Actor multiple times - a friction point that helps prevent accidental data broker accumulation. *** **Document Version:** 4.0 (anonymous Publisher, UnseenUser identified) **Last Updated:** May 5, 2026 **Master ToS Version:** 4.0 **TikTok Suite Notes:** This Actor is part of the UnseenUser TikTok atomic actor suite. Companion actors: - Transcript Extractor - Audience Geography - Keyword Search - Sound Tracker - Comments & Replies - Live Status - User Search - Followers & Following (this Actor) # Actor input Schema ## `handles` (type: `array`): One or more TikTok handles and/or full profile URLs (one per line). Each entry can be a bare handle, an @handle, or a `https://www.tiktok.com/@handle` URL. Multiple entries are processed sequentially with isolated error handling: a failure on one entry does not stop the others. ## `get_followers` (type: `boolean`): Include the list of followers in the output. ## `get_following` (type: `boolean`): Include the list of accounts the creator follows in the output. ## `max_users_total` (type: `integer`): Hard cap on the total number of users returned per run (across all handles). ## `max_pages_followers` (type: `integer`): Maximum number of paginated pages to fetch for followers, per handle. ## `max_pages_following` (type: `integer`): Maximum number of paginated pages to fetch for following, per handle. ## Actor input object example ```json { "handles": [ "stoolpresidente", "https://www.tiktok.com/@barstoolsports" ], "get_followers": true, "get_following": true, "max_users_total": 5000, "max_pages_followers": 50, "max_pages_following": 50 } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("unseenuser/tiktok-followers-following-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("unseenuser/tiktok-followers-following-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call unseenuser/tiktok-followers-following-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=unseenuser/tiktok-followers-following-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "TikTok Followers & Following Scraper [NO LOGIN] ✅", "description": "Bulk-scrape any TikTok user's followers and following lists. Get handles, names, follower counts, bios, regions. Built for lead gen, network mapping, influencer research, and ICP validation. No login, no cookies. Cheaper than every cookie-based alternative.", "version": "0.0", "x-build-id": "9D6KQPM4BggGznqKm" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/unseenuser~tiktok-followers-following-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-unseenuser-tiktok-followers-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/unseenuser~tiktok-followers-following-scraper/runs": { "post": { "operationId": "runs-sync-unseenuser-tiktok-followers-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/unseenuser~tiktok-followers-following-scraper/run-sync": { "post": { "operationId": "run-sync-unseenuser-tiktok-followers-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "handles" ], "properties": { "handles": { "title": "TikTok handles or URLs", "minItems": 1, "uniqueItems": true, "type": "array", "description": "One or more TikTok handles and/or full profile URLs (one per line). Each entry can be a bare handle, an @handle, or a `https://www.tiktok.com/@handle` URL. Multiple entries are processed sequentially with isolated error handling: a failure on one entry does not stop the others.", "items": { "type": "string" } }, "get_followers": { "title": "Fetch followers", "type": "boolean", "description": "Include the list of followers in the output.", "default": true }, "get_following": { "title": "Fetch following", "type": "boolean", "description": "Include the list of accounts the creator follows in the output.", "default": true }, "max_users_total": { "title": "Max users per run", "minimum": 1, "maximum": 50000, "type": "integer", "description": "Hard cap on the total number of users returned per run (across all handles).", "default": 5000 }, "max_pages_followers": { "title": "Max followers pages per handle", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Maximum number of paginated pages to fetch for followers, per handle.", "default": 50 }, "max_pages_following": { "title": "Max following pages per handle", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Maximum number of paginated pages to fetch for following, per handle.", "default": 50 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```