TikTok Profile Scraper

Yes — a public account's videos are public data. Captions, view counts and follower numbers are there for anyone who opens the profile, and we collect nothing a visitor could not. Details in our guide to the legality of web scraping.

No login required. No TikTok account, no cookie, no session to sync, nothing to install. Paste a profile URL or just the handle and hit run — that is the entire setup, which is rarer than it should be.

66 data points per video. Description, hashtags and mentions, publication date, plays, likes, comments, shares, saves and reposts, length, video, cover and download links, subtitles, music title and copyright status — plus the account's bio, badge and follower counts.

Around 500 videos a minute. Five accounts are collected side by side, so a whole roster of creators moves almost as fast as a single profile. A back catalogue of a few thousand videos is a coffee break, not an afternoon.

Everything the profile feed will give up. Leave it uncapped for the entire back catalogue, or set a limit per profile or per run when you only want a taste. Private accounts are the one exception — nothing public, nothing to scrape.

Yes — switch on Profile Only. The account comes back as a single row: nickname, bio, bio link, avatar, verified badge, followers, following, total likes, video count and the date the account opened. One credit, no videos.

Yes — Newer Than stops at a date. Give it a window like 24h, 7d or 2w, or a fixed date, and anything older is left where it is. Put it on a daily schedule and each run brings back only what was posted since the last one.

Yes — pile as many profiles into the list as you like, full URLs or bare handles, mixed freely. Five are collected at once and every row names the account it came from, so an entire roster lands in one export.

Yes — every row carries direct media links. The video itself, the download link, the cover and the animated cover, the slideshow images for photo posts, and the subtitle tracks whenever the creator published them. Music links come too.

Wherever your workflow already lives. Google Sheets, Make, n8n, Amazon S3, email and webhooks — plus our MCP server, so Claude or ChatGPT can start a run and read the results itself. CSV, Excel and JSON downloads as well. See all integrations.

URL, such as https://www.tiktok.com/@nba. Paste thousands at once or upload a CSV; duplicate inputs are skipped. 4 settings shape the run: see them in the playground.

66 data attributes per video, each with its description and an example: see the full list.

No. Duplicates are removed, and you only pay for unique results.

As fresh as your run: each run collects the data from the site at the moment it runs, nothing comes from a stored database.

CSV, Excel or JSON from the dashboard, through the API, or sent after every run to Google Sheets, Amazon S3, an SFTP server, a webhook or by email.

7 days on the free plan, 28 days on paid plans. Then they are deleted. Download or deliver what you want to keep.

Around 500 videos a minute for one squid. Your plan's slots run several squids at the same time.

100.00% of its runs had no incident over the last 90 days (0 incidents, 100% fixed). Every day is on this page.

Our team fixes the scraper: every scraper on lobstr.io is built and maintained by us. How we measure.

Yes, on paid plans: every hour, every day, every weekday or on a custom schedule, in your time zone.

Yes: set the most results per task and per run in the settings. The run stops there and so does the bill.

1 credit per result. The playground shows the price as you pick them.

Yes. The free plan gives 100 credits every month, 100 results with this scraper, with exports capped at 30 rows.

Every month a plan gives credits, which pay for results, and slots, which set how many squids run at the same time. Starter: $20 for 10,000 credits; Pro: $100 for 100,000 credits; Team: $500 for 1,000,000 credits. Upgrades start right away and are prorated; downgrades and cancellations take effect at the end of the cycle.

No. Your credits refresh every month with your plan.

You choose, per squid: pause and pick up where it stopped, or end the run. To keep going, upgrade or reset your billing cycle: your plan renews right away and your credits come back. Auto Billing Reset does it for you when your usage crosses a threshold you set.

Yes: paying yearly takes 20% off every plan.

A monthly plan: within 10 days of the charge, if no credit was used in that period. A yearly plan: within 30 days, in full if no credit was used, otherwise minus one month. Cancel from your billing page, then write to contact@lobstr.io. The details are in the terms of use.

Collecting publicly available data is generally allowed, but you choose what you collect and you are responsible for how you use it. Our terms of use (article 6) ask every user to respect the rights of the sites, not to extract substantial parts of a database, not to access confidential data and to follow personal data law such as the GDPR. This is not legal advice.

When results contain personal data, you are the data controller and lobstr.io, a French company, processes them on your behalf, under our personal data agreement. You need a lawful basis for what you collect, must inform the people concerned and honor their requests.

Results: 7 days on the free plan, 28 days on paid plans, then they are deleted; you can delete them sooner. Your account data: see the privacy notice.

Yes, through the REST API at https://api.lobstr.io/v1, with your key from the dashboard. The playground’s Code tab writes the calls for your settings, in cURL and Python. The documentation has the full reference.

Yes. Add our MCP server, https://mcp.lobstr.io/mcp, to Claude, ChatGPT, Cursor or any MCP client and sign in with lobstr.io. Your agent shows the cost and asks you before a run spends credits. The playground’s Agent tab gives you a prompt.

No. Credits pay for results, not for requests.

Yes. Point a webhook at your server and lobstr.io calls it when a run succeeds or fails.

Yes, per endpoint: 120 requests a minute on squids and runs, 90 on tasks, 2 a second on results. Above that the API answers 429 with a Retry-After header.