Cheapest TikTok Profiles: Small Batches | $0.25/1K Lookups avatar

Cheapest TikTok Profiles: Small Batches | $0.25/1K Lookups

Under maintenance

Pricing

$0.25 / 1,000 successful api requests

Go to Apify Store
Cheapest TikTok Profiles: Small Batches | $0.25/1K Lookups

Cheapest TikTok Profiles: Small Batches | $0.25/1K Lookups

Under maintenance

Public TikTok profile by handle: bio, links, verification and follower, following, heart and video counts. One profile per request at $0.25 per 1,000 requests; no startup fee.

Pricing

$0.25 / 1,000 successful api requests

Rating

0.0

(0)

Developer

Lite Scraper

Lite Scraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Public TikTok profile by handle: bio, links, verification and follower, following, heart and video counts. One profile per request at $0.25 per 1,000 requests; no startup fee.

Public TikTok profile details and follower, following, like and video counts.

Price

$0.25 per 1,000 lookups ($0.00025 per successful API response). A lookup is one successful source response for the supplied identifier. Fields and records included in that response cost no extra.

Each successful response saved to the run is one paid event, including valid empty responses. Multiple places, reviews, or products in one response do not create additional paid events.

Failed requests are unbilled. JSON output is saved before successful responses are charged together. Recovery never recharges an ambiguous payment after its safe retry window; the saved output remains available for reconciliation. There is no Actor startup fee or separate per-row fee; platform usage during the run is included. Standard Apify charges for post-run storage access may still apply. Payments are handled by Apify; no separate service key or proxy purchase is required.

Free-plan users receive up to 25 successful requests per Apify user per UTC day across this catalog, subject to the service trial allowance. Paid runs respect the input request limit and Apify spending limit.

Quick start

Use a single input below, or supply requests as a list of parameter objects. Top-level API fields are shared defaults, and each batch object overrides them. Identifiers in examples demonstrate the format; use an identifier returned by the matching provider for production work.

{
"handle": "tiktok",
"maxRequests": 10,
"maxPagesPerInput": 1
}

Input parameters

FieldTypeRequiredMeaning
handlestringOptional / conditionalPublic TikTok handle, with or without @; supply this or user_id.
timeoutnumberOptional / conditionalTotal request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.
user_idstringOptional / conditionalNumeric TikTok user ID; supply this or handle.

The source validates conditional parameter combinations. Validation errors do not trigger a paid request event. Provider availability determines which optional result groups appear.

Batches, pagination, and limits

  • requests: up to 1,000 input parameter objects in one run.
  • maxRequests: total successful API requests, including pages; default 100. At that limit the event price is at most $0.025.
  • maxPagesPerInput: default 1. Increase to follow native continuation links where this endpoint supplies them. No synthetic pagination is invented.
  • maxResults: maximum dataset rows; default 1,000. Already in-flight requests can complete and be billed, with full JSON saved even if their rows exceed this cap.
  • maxConcurrency: default 2, maximum 8. Service capacity and trial limits may reduce it.
  • includeArtifacts: optionally retain available raw source artifacts in this run. Default false.
  • datasetOutput: default false. Enable the dataset/export workflow; pagination and artifacts select it automatically. JSON mode uses 128 MB, allows up to 1 MiB per upstream response and 8 MiB total output. Use dataset output for larger responses.

Output

The default JSON workflow saves one OUTPUT record with successfulRequests, failedRequests, and ordered results. Each result contains requestId, statusCode, and the complete source JSON in body. Use the run-sync API to return OUTPUT directly. It does not create dataset rows or per-request response copies.

With datasetOutput: true, pagination, or artifacts enabled, the default dataset contains source records with requestId, inputIndex, page, group, readable title, url, rating, and text fields when available, the complete record in data, and responseUrl. A successful response without a primary result group gets a response row.

In the dataset workflow, each responseUrl points to a stored response envelope; its response.body contains the complete API JSON, including optional modules and pagination. SUMMARY reports successful requests, failures, row count, and event charges. ERRORS records unsuccessful requests. If every request fails, the run fails with no request-event charges.

Follow-up API links, including pagination and related reviews or products, are Apify request objects: { "url": "https://api.apify.com/v2/actors/litescrape~<actor>/runs", "method": "POST", "input": { ... } }. POST the supplied input as JSON to url using your own Apify authorization header. Each follow-up starts a new run limited to one successful request; use maxPagesPerInput for automatic pagination inside this run. Source website links are unchanged. search_metadata.json_endpoint links to the saved Apify response. Available artifact links point to files copied to Apify; unavailable artifact links are omitted.

JSON exports preserve nested fields. Select the flat overview fields for CSV. Artifact manifests use artifacts-<requestId> keys and link to copied source files when available. Private run data requires the appropriate Apify access.

Price comparison

Lowest price in this 2026-10-19 comparison for runs of up to 100 single-profile lookups, one public profile per billed request.

Illustrative workload: 100 successful requests × 1 usable profiles per request = 100 profiles. Our total is $0.025, equivalent to $0.25 per 1,000 profiles.

These are calculated prices, not measured scraper runs or guaranteed page yields. Count unique usable source records actually delivered, including the cost of empty responses, continuation pages and lookups needed to obtain the fields you need. An array of request objects does not turn multiple API calls into one billed request.

ActorLowest applicable tierPublished-charge subtotal for this workloadEffective price / 1,000 output units
LitescrapeSame request rate on every plan$0.025$0.25
dami_studio/tiktok-scraper (active prices)GOLD$0.0254$0.254
xmolodtsov/tiktok-profile-scraper (active prices)GOLD$0.06$0.6
fetch_cat/tiktok-profile-scraper (active prices)DIAMOND$0.049047$0.49047
automation-lab/tiktok-profile-scraper (active prices)DIAMOND$0.0865$0.865
cleansyntax/tiktok-profile-scraper (active prices)FREE$0.1$1
karamelo/tiktok-profile-scraper (active prices)GOLD$0.15$1.5
novi/tiktok-user-info-api (active prices)GOLD$0.4505$4.505

Each competitor gets its lowest published tier, including enterprise tiers, without adding a plan subscription cost. Required compared events use the same tier; known startup charges assume one run and the minimum one billed GB. Unquantified compute/proxy charges, optional enrichment and any omitted additional fees can only increase the displayed competitor subtotal. Output completeness and reliability were not benchmarked.

  • dami_studio/tiktok-scraper: Profile row only, with Results per input set to 1; its default adds about 10 video rows per handle.
  • At 1,000 profiles in one run, Dami's Studio costs $0.245 ($0.244/1K rows at Gold and above plus a $0.001 start) versus our $0.25, so the claim is limited to small batches. Below about 166 profiles per run its start fee makes ours cheaper.
  • Profile-and-videos scrapers that charge per post (Clockworks, API Dojo) are a different operation and are not counted here; see the TikTok Profile Videos Actor.

Cheapest means the lowest calculated price for the stated workload among the named paid Apify Actors in this dated audit. It is not a claim about every Actor, every plan, every workload, or equal output quality. Free/platform-only Actors, monthly rentals and bring-your-own-paid-key wrappers do not establish a comparable fixed total from their Actor fee alone. They may cost less on particular workloads.

The comparison uses the linked active pricing snapshots and public documentation checked on the audit date. Recheck live pricing before relying on a competitor comparison. No provider affiliation or equal-quality claim is implied.

Support

Use this Actor's Issues tab on Apify and include the run ID plus a description of the unexpected result. Do not post credentials.

This is an independent tool from Litescrape. Provider names identify the source; they do not imply affiliation or endorsement.