Instagram Scraper: Profiles, Posts, Reels & Comments

Scraping is asynchronous: submit a run → poll status → fetch data. See Quick Start for the full end-to-end flow, and Auth & Error Handling for the shared envelope, run state machine, billing, and error codes. This page only lists each endpoint's submit parameters (target fields) and output record fields.

At a Glance

• Base URL: https://api.antsdata.com/v1
• Submit a run: POST /v1/scraper/instagram/<resource>, body { deliveryMode, recordLimit, targets:[…] }

💡 You can also use deliveryMode: "sync" (small jobs block until terminal, auto fallback to polling on timeout) — see quick-start · Sync mode.

• Auth: header Authorization: Bearer ants_xxxxxxxxxxxx (static API Key)
• Content-Type: application/json
• targets: array input (≥1); each element's fields = the endpoint's "target fields" table below. Per-target success/failure lives in the run's tasks[], not in the result records.
• Fetching data: submit returns 201 + { id, status:"queued" }; poll GET /v1/scraper/runs/{id} until succeeded, then page through records or download by id (see Quick Start).

Endpoints

Profile — Account Profiles

Scrape the public profile of one or more accounts.

Endpoint: POST /v1/scraper/instagram/profile

Target fields (each element of targets[]):

Output record fields (each item in records):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/instagram/profile" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      { "username": "nike" },
      { "username": "instagram" }
    ]
  }'

Returns 201 + { "id": <run id>, "status": "queued" }; then poll and fetch data by id (see Quick Start).

Posts — Account Posts

Scrape the posts published by a given account.

Endpoint: POST /v1/scraper/instagram/posts

Target fields (each element of targets[]):

The number of posts returned per account is controlled by the run's recordLimit (default 1000).

Output record fields (each item in records):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/instagram/posts" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 500,
    "targets": [
      { "username": "nike" }
    ]
  }'

Returns 201 + { "id": <run id>, "status": "queued" }; then poll and fetch data by id (see Quick Start).

Reels — Account Reels

Scrape the Reels published by a given account.

Endpoint: POST /v1/scraper/instagram/reels

Target fields (each element of targets[]):

The number of Reels returned per account is controlled by the run's recordLimit (default 1000).

Output record fields (each item in records):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/instagram/reels" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 300,
    "targets": [
      { "username": "nike" }
    ]
  }'

Returns 201 + { "id": <run id>, "status": "queued" }; then poll and fetch data by id (see Quick Start).

Comments — Post Comments

Scrape comments by post URL.

Endpoint: POST /v1/scraper/instagram/comments

Target fields (each element of targets[]):

The number of comments returned per post is controlled by the run's recordLimit (default 1000).

Output record fields (each item in records):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/instagram/comments" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 200,
    "targets": [
      { "post": "https://www.instagram.com/p/DZyno24tbY2/" }
    ]
  }'

Returns 201 + { "id": <run id>, "status": "queued" }; then poll and fetch data by id (see Quick Start).

Fetching Data & Lifecycle

After submitting a run:

1. Poll: GET /v1/scraper/runs/{id} until status reaches a terminal state succeeded / failed (backoff 1s→2s→5s recommended).
2. Fetch: once succeeded, page through records with GET /v1/scraper/runs/{id}/records?page=1&pageSize=20, or download the full result with GET /v1/scraper/runs/{id}/download?format=json|csv|excel.
3. Partial success: a failing target does not affect the others — it is marked tasks[].status=failed with an errorMessage, and as long as ≥1 target succeeds the run is succeeded and returns records for the successful ones.

For full field definitions, the run state machine, billing, and error codes, see Auth & Error Handling.

FAQ

Q: Can I scrape multiple accounts / posts at once?

Yes. targets is an array; one run can hold multiple targets, executed in parallel, with per-target status in the run's tasks[].

Q: What happens with private or non-existent accounts?

That target is marked status:"failed" with an errorMessage in tasks[]; the other targets still return data and the run can be succeeded.

Q: Am I charged for failed scrapes?

No. Billing settles on the number of records successfully produced; if all targets fail the hold is released and nothing is charged (see Auth & Error Handling).

Q: What is recordLimit?

The record cap per target (default 1000). For example, on the posts endpoint with 3 username targets and recordLimit: 500, each account yields up to 500 posts.

Next Steps

• Platform guides: TikTok · X · Instagram · Facebook · LinkedIn · Google · YouTube · Amazon
• Synchronous search: Google SERP
• Auth & Error Handling — Unified envelope, run state machine, billing & error codes