Recent Posts Scraper - Instagram, TikTok & X

Find recent posts from known creator profiles

Collect recent public posts from known Instagram, TikTok and X creator accounts. YouTube discovery is not currently configured, and Facebook timelines are not supported. This is account-based collection, not search or niche discovery.

Use this recent posts scraper to review a creator's available recent content, collect post URLs for follow-up metrics refreshes, or feed your own content-review spreadsheet. Get a consistent dataset across the three supported platforms without supplying social logins or proxies.

Quick start

1. Open the Actor in Apify Console and paste an Instagram, TikTok or X profile URL.
2. Start with a few posts per account and a small run spending limit, then click Start.
3. Export JSON, CSV or Excel from the dataset. Read OUTPUT for each account's coverage, stop reason and collection window.

{"urls":["https://www.tiktok.com/@nasdaily"],"maxPostsPerAccount":20,"maxResults":100}

Window and coverage

The window is fixed to the trailing 21 days when each source collection begins. Returned post metrics are cumulative observations, not engagement gained during those 21 days. Up to 200 posts per account and 1,000 globally can be delivered. Supply no more than 10 known profile URLs.

TikTok has a paginated creator feed. Instagram can fall back to a bounded authored-reel preview; X currently uses a bounded public-originals preview. Those sources stay explicitly partial. YouTube account collection requires maintainer-side YouTube provider configuration; at initial catalog setup that key was not configured, so YouTube discovery is not currently ready even though ordinary YouTube post/profile refresh works. Do not use this Actor for YouTube discovery until this availability note is updated.

The default dataset contains post records from the specific completed collection, with canonical post URL, platform ID, available metrics and observation timestamp. OUTPUT adds per-source coverage, stop reason and window. An empty/failed/partial result is not proof that the account has no other posts. Unknown fields remain null.

Example output

Illustrative excerpt, not live data:

{
  "sourceUrl": "https://x.com/example",
  "platform": "x",
  "status": "succeeded",
  "url": "https://x.com/example/status/1234567890",
  "postId": "1234567890",
  "caption": "An illustrative post.",
  "imageUrl": "https://images.example/post.jpg",
  "metrics": { "views": 1200, "likes": 40, "comments": null, "shares": null, "bookmarks": null },
  "observedAt": "2026-09-09T12:00:00.000Z",
  "collectionScope": "sync_specific_collection",
  "syncCoverage": "partial"
}

sourceUrl identifies the input account; url identifies the collected post. Keep both when joining datasets. Available metrics may differ by platform. Collection membership is specific to the source sync; the post's observation timestamp should still be checked before treating metrics as current.

imageUrl is the post image or video cover when the source exposes one, otherwise null. It is additive for compatibility with older runs and never delays post delivery.

Limits and cost

Launch price: $3 per 1,000 delivered post records, with no separate account-refresh or source-status charge. Apify platform usage may apply separately. The Console pricing tab is authoritative.

For example, 100 delivered posts generate $0.30 in result charges. Requested limits are ceilings, not promised yields. A new run may collect and charge for posts already returned in an earlier run.

Run spending and result caps are enforced before more source work is admitted. Use resultId for deduplication after interrupted delivery. Aborting stops new admission but backend work already submitted can finish. No customer social login, proxies or SIN credentials are needed.

Built and maintained by NooEsc, powered by SIN. Public content only; no followers lists, private accounts, DMs or unrestricted historical archives.

API, workflow and support

Use this Actor's API tab for request and SDK examples. To revisit collected posts later, pass their url values to Post Metrics. Each Actor run is separately priced; this does not automatically create recurring tracking.

Need follower counts or bios instead? Use Account Profiles. Need the comments on a collected post? Use Public Comments, which reports its own coverage limits.

Ask for help in the Issues tab. Include a run URL and the unexpected result, never cookies, tokens or private data.