MADE TO FIT YOUR WORKFLOW

Start with a URL.
Build with structured data.

The integration API is available to enabled integration customers. Try the public web viewer first. Keep API keys on your own server.

Create a collection job cURL

curl -X POST 'https://reels.adsinch.com/api/v1/reels/integrations/jobs' \
  -H "Authorization: Bearer $REELTRACK_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: your-unique-request-key' \
  -d '{
    "url": "https://www.facebook.com/reel/REEL_ID",
    "max_comments": 500,
    "include_replies": true,
    "max_replies": 1000,
    "comment_order": "default",
    "max_depth": 10,
    "deadline_seconds": 900
  }'

Replace REEL_ID with a real video ID. This example shows the request format and does not execute it.

CLEAR EXPECTATIONS

Know the scope before you build.

Product	Current scope	What to expect
Single-Reel viewer	Up to 500 top-level comments + 1,000 replies	Publicly accessible Reels using the standard comment connection. See the console for guest quotas.
Page management	10 Pages / 180 days / 300 top-level comments per Reel	The current Page workflow collects top-level comments only, without replies.
Integration API	Explicit request limits, subject to customer quotas	Standard mode is the default; All requires an explicit choice. The actual source order in standard mode may be unspecified.
Media & authors	Public fields actually returned by the source	Fields may be missing. Author profiles are not crawled individually. Media files are not downloaded, and URLs may expire.
Apify	Adapter in development	A local adapter package exists. It is not yet listed in the Apify Store, and automated billing is not enabled.

Results may be partial when limits are reached or the source restricts access. Missing fields are null. Hidden comments, every author detail, and all media URLs cannot be guaranteed.

ONE DATASET, THREE DELIVERY OPTIONS

From a batch to your pipeline.

Visitor batch collector

Paste up to 10 Reel links. The collector submits them one at a time, loads every saved results page, and provides merged CSV, structured JSON and a ZIP with one CSV/JSON pair per ready job.

One active job per visitor session; 10 new jobs per day. The manifest preserves failed, cancelled and pending links.

Collect your links →

Integration API

Enabled customers use server-side Bearer keys and their assigned quotas. Persist the job ID and idempotency key, poll status, then read result cursors and the final receipt. Request cancellation when needed.

Keys are provisioned for enabled customers. Self-service billing and Webhook delivery are not available in the current API.

Check scope & limits →

Apify adapter

The local adapter accepts 1–100 Reel links, with per-Reel limits and configurable task concurrency. It persists job IDs and cursors for recovery, and delivers comments, replies, Reel summaries and explicit error rows.

Operator-owned API secrets and verified Apify consumer namespaces are required. Store publication and automatic billing are pending.

See Actor input →

ADAPTER INPUT EXAMPLE

Run the same collection workflow on Apify.

{
  "urls": ["https://www.facebook.com/reel/REEL_ID"],
  "commentOrder": "default",
  "maxComments": 500,
  "includeReplies": true,
  "maxReplies": 1000,
  "maxDepth": 10,
  "concurrency": 4,
  "deadlineSeconds": 900
}

This is the local adapter's input format, not a link to a published Actor. Integration customer quotas still apply. API credentials belong in operator secrets, never Actor input, datasets or browser code.

SOURCE FIELDS, WITH THEIR CONTEXT

Know what each export means.

Category	Source-backed fields	Meaning
Author	ID, name, profile URL, avatar, verification, observed type/badges	Source IDs stay strings. Unknown verification stays null. Individual profiles are not crawled.
Thread	Comment ID/permalink, parent ID, depth, source reply total, saved child count	Source totals and collected replies are different fields. Original GraphQL IDs are preserved.
Engagement	Reaction total/breakdown, exact Like count, raw abbreviated values	A reaction total is not an exact Like count. Estimates and missing values remain explicit.
Media	HD/SD MP4 URLs, cover, duration, publisher and capture time	Availability depends on source responses. URLs can expire; media files are not retained.
Evidence	Final status, requested limits, coverage, result count and snapshot receipt	Partial results and source restrictions remain visible. Exports contain the saved dataset, not a guarantee of every Facebook comment.

Live collector CSV uses the same 53-column export as the existing console. The Playground is a smaller synthetic example.

Explore the output. Then build with it.

Explore sample data →