YouTube, TikTok & Instagram Video-to-Profile Resolver

Social Video Profile Resolver converts supported YouTube, TikTok, and Instagram video/post URLs into creator-channel or profile links. Mix URLs or an accessible Apify dataset for attribution and cleanup.

A resolved link is not verified account ownership or proof that a video is public and live. Some inputs resolve entirely from a username/channel ID embedded in the URL, without fetching the video. These successful pattern-based rows incur the same result event as network-based resolutions.

The Actor uses URL parsing and direct HTTP, without a browser or configured proxy. It asks for no social-platform login or user-provided platform API key. Apify API runs still require an Apify token and incur startup, result, and separately billed platform usage.

Resolution methods and supported URLs

Platform	URL forms and methods
YouTube	Creator-qualified `@handle/shorts
TikTok	@user/video/... and @user/photo/... use url_pattern. Other links try oembed; recognized vm.tiktok.com, vt.tiktok.com, and /t/ short links can fall back to redirect parsing or another oEmbed request.
Instagram	Creator-qualified `username/reel

Network paths can involve retries, redirects and fallbacks, not a fixed one-request-per-input cost. Instagram metadata parsing is heuristic and may select a mentioned account rather than a verified owner. Preserve method for attribution. The tool returns profile links, not statistics, contacts, video engagement, histories, private content or media files.

Quick start

{
  "videoUrls": [
    "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
    "https://www.tiktok.com/@scout2015/video/6718335390845095173",
    "https://www.instagram.com/reel/DR9EITCjN1w/"
  ],
  "maxConcurrency": 3,
  "instagramConcurrency": 1,
  "includeFailed": true
}

Illustrative inputs, not verified availability/ownership. Save as input.json for a billable API run:

curl -X POST \
  'https://api.apify.com/v2/acts/funny_ground~social-video-profile-resolver/run-sync-get-dataset-items' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data-binary @input.json

Input fields and bulk behavior

Field	Default	Behavior
videoUrls	unset	Array of supported video/post URL strings; platforms can be mixed.
inputDatasetId	unset	Optional accessible Apify dataset, read in 1,000-item pages; combined with inline URLs. Must not be this run's output dataset.
urlField	"url"	Top-level string field holding a video URL in each dataset item.
maxConcurrency	50	Concurrent input tasks; 1–200.
instagramConcurrency	15	Instagram tasks; 1–50, additionally capped by overall concurrency.
maxRequestRetries	3	Retries per HTTP request; 0–10.
requestTimeoutSecs	20	Per-request timeout; 5–120 seconds.
includeFailed	true	Save failed-item diagnostics; false omits these rows, not their request/start/usage costs.

Supply inline URLs or inputDatasetId. Schemes can be omitted; credential-bearing URLs and URLs over 4,096 characters are rejected. Never include access tokens or secrets.

No URL/creator deduplication: repeated inputs, different videos from one creator, and inline/dataset overlap can each produce a row and custom result event. Deduplicate separately if you need unique creators.

Developer Free-plan preview: 50 saved rows globally, including diagnostics, which reduce successful-row capacity. Paid plans remove this developer cap, not other constraints. FREE-tier events still cost money. Concurrent completion means the preview is not necessarily the first 50 inputs by index.

Output and summaries

Successful rows contain index, inputUrl, status: "ok", platform, profileUrl, resolvedUrl, method, attempts, and resolution timestamp crawledAt. Available creatorUsername, creatorName, and httpStatus depend on the method. A YouTube username can be a channel ID; crawledAt is not a post publication date.

url_pattern has attempts: 0 and no HTTP verification. redirect_pattern derives a TikTok profile from a redirect path. oembed uses returned author metadata; seo_meta is heuristic. None independently verifies ownership.

Failures contain status: "failed", errorCode, error, attempts and available platform/URL/HTTP context. Invalid URLs, access denials, rate limits or missing metadata can fail; recognized creator-qualified paths can instead succeed even for private, removed, fabricated or stale posts.

Batches follow completion order; use index for input association. Disabled diagnostics and Free-plan/event limits mean there may be fewer rows than inputs. The key-value record OUTPUT separates processed/resolved totals from saved/charged successes. All-failed or zero-success batches can still finish SUCCEEDED; inspect rows and summary rather than trusting run status as a quality check.

Custom-event billing and current pricing

Successful batches use Actor.pushData(rows, "profile-resolved") and its returned charge count. This custom event—not apify-default-dataset-item—bills each saved successful input row, including zero-request pattern successes, not unique creators. No separate per-request event is configured.

Failed diagnostics bypass the custom event through the opened dataset. They have no profile-resolved fee, but still consume preview/storage capacity and may incur startup, compute and transfer costs.

Apify plan	Per profile-resolved event	Per 1,000 events
FREE	$0.00225	$2.25
BRONZE	$0.00045	$0.45
SILVER, GOLD, PLATINUM, DIAMOND	$0.00040	$0.40

apify-actor-start costs $0.00005 per allocated GB, minimum one event per run, not a universal fixed fee. The running user separately pays compute, transfer and storage, including empty/failed-run usage. No downstream Actor, customer scraping-key input or proxy is configured.

See the Pricing tab. Budget-aware batches can omit resolved items; an event budget neither guarantees full output nor caps all platform costs.

FAQs and responsible use

Does ok verify a live creator/video? No. Check method: patterns are unverified URL identities; public metadata is source-derived attribution.

Are private/deleted links always unbilled? No. Only actual failed rows have no custom result event. Pattern successes can be billed regardless of availability; start and usage remain separate.

Can I collect videos from resolved profiles? Use them as creator-video input candidates after checking ambiguous results. That collection has separate costs and limits.

Platforms may rate-limit or withhold public metadata, change redirect behavior, or return login/region/age restrictions. The resolver does not bypass authentication or private-content controls. Use public data under applicable law, platform terms, and privacy requirements.

Complementary Actors

• Social Creator Videos Scraper — bounded public creator-video feeds after profile resolution.
• YouTube Scraper — channel/search/playlist/direct-video metadata.
• Instagram Reels & Video Scraper — available post details, counters, and temporary media links.