Pixiv Artwork Comments Scraper

Pixiv Artwork Comments Scraper — Collect public Pixiv artwork comments with pagination. Export text, stamps, author details, dates and reply indicators as individual comment records. Add supported inputs and start a run to get structured public data without providing a Pixiv account.

Export root comments on a public Pixiv artwork with text, dates and author links. Use the records for manual feedback review without collecting reply trees.

At a glance	Details
📥 Input	Positive Pixiv artwork IDs or public /artworks/ID URLs.
📤 Output	One comment per success row, with source input retained
📄 Pagination	pagesPerArtwork limits result pages per input, with a default of 1. The source may end sooner.
🔐 Login required	No
⚡ Processing	Up to 5 HTTP requests concurrently with automatic retries
💾 Delivery	One Apify dataset view, useful flat columns and complete nested JSON

What the pixiv artwork comments scraper collects 📊

Collect public Pixiv artwork comments with pagination. Export text, stamps, author details, dates and reply indicators as individual comment records.

Data can include:

• Source identity and public links
• Available id, artwork id, artwork url, text, stamp id, created at, parent comment id, has replies
• Original input retained with every result
• One consistent success or failed record format

How to collect comments from Pixiv 🚀

1. Enter one or more supported inputs in inputList.
2. Set the result-page budget for each input.
3. Start the Actor.
4. Open the Comments dataset view and review the individual records.
5. Export the dataset or retrieve it from your application.

{
  "inputList": [
    "149440738"
  ],
  "pagesPerArtwork": 1
}

pagesPerArtwork limits result pages per input, with a default of 1. The source may end sooner.

Pixiv comments data and complete output 📦

Field	Type	Meaning
status	string	Result status: success or failed.
input	string	Original submitted input.
id	string or null	Stable ID of the result entity, retained as a string.
artwork_id	string or null	Artwork id supplied by the source.
artwork_url	string or null	Available artwork URL.
text	string or null	Public text of this result.
stamp_id	string or null	Stamp identifier for sticker comments; text may be empty.
created_at	string or null	Source publication or comment time. Comment timestamps retain the source format and do not invent a timezone.
parent_comment_id	string or null	Parent comment id supplied by the source.
has_replies	boolean or null	Whether Pixiv reports replies; this Actor exports root comments only.
author_id	string or null	Author id supplied by the source.
author_name	string or null	Author name when exposed by the public response.
author_url	string or null	Available author URL.
author_avatar_url	string or null	Available author avatar URL.
is_deleted_author	boolean or null	Is deleted author when exposed by the public response.

Nested arrays and media references stay in their parent record. Downloading source media files is not part of this Actor.

Every top-level output field appears in these complete examples. The success example is normalized from a public response. Long strings and arrays are shortened here; the Actor keeps the complete available values. Values are a snapshot and can change. Nested arrays remain inside their parent result.

Representative success result with every output field (long text and arrays shortened for readability):

{
  "status": "success",
  "input": "149440738",
  "id": "233790478",
  "artwork_id": "149440738",
  "artwork_url": "https://www.pixiv.net/en/artworks/149440738",
  "text": "super small and cute",
  "stamp_id": null,
  "created_at": "2026-09-12 01:49",
  "parent_comment_id": null,
  "has_replies": false,
  "author_id": "128698987",
  "author_name": "AzaArtsymates",
  "author_url": "https://www.pixiv.net/en/users/128698987",
  "author_avatar_url": "https://i.pximg.net/user-profile/img/2026/09/08/09/06/57/29307681_81ece73921f7ea68a426e957c972b711_170.png",
  "is_deleted_author": false
}

Complete failed result:

{
  "status": "failed",
  "input": "invalid input",
  "id": null,
  "artwork_id": null,
  "artwork_url": null,
  "text": null,
  "stamp_id": null,
  "created_at": null,
  "parent_comment_id": null,
  "has_replies": null,
  "author_id": null,
  "author_name": null,
  "author_url": null,
  "author_avatar_url": null,
  "is_deleted_author": null
}

A failed row preserves input, sets status to failed, and sets every other top-level field to null. The run log records the reason. Optional successful fields can be null or empty when Pixiv does not supply them. Object fields are exposed through useful columns in the single Comments view; arrays are not expanded into extra result rows.

Input requirements and pagination settings ⚙️

Parameter	Type	Required	Default	Rules
inputList	array of strings	Yes	None	Positive Pixiv artwork IDs or public /artworks/ID URLs. At least 1 item.
pagesPerArtwork	integer	No	1	Maximum result pages per input. Setup requests do not count as pages. Stops when the source has no next page or repeats a continuation. Actual rows per page can vary. Minimum 1.

Positive Pixiv artwork IDs or public /artworks/ID URLs.

Examples of supported inputs: 149440738.

Duplicate normalized inputs are processed once. Within the collection for one source input, repeated records are removed while distinct interactions or objects remain separate. The same object returned for different source inputs retains its source relationship.

The first result page counts as page 1. Public-page preparation and metadata lookups do not consume result pages. Collection stops at your page budget or the end of the available list. A short page alone does not mean that the list has ended.

Pixiv comments use cases 🎯

Review public feedback on a Pixiv artwork

Export root comments on a public Pixiv artwork with text, dates and author links. Use the records for manual feedback review without collecting reply trees.

Research stamp responses on a Pixiv artwork

Collect root comments on a selected Pixiv artwork. Compare text comments and stamp identifiers in your own analysis; stamp-only text can be empty.

Identify Pixiv comments with available replies

Collect root comments from selected Pixiv artworks. Use the has_replies flag to identify threads for manual review; nested replies are not collected.

Pricing and saved-result behavior 💰

Check the Actor’s Pricing tab for the active pricing model and current rate. Store settings can change, so this README does not claim a fixed price or runtime.

Under dataset-item pricing:

• Each successful result represents one comment for its source input.
• An invalid or unavailable input, an input with no accessible results, or an exhausted request can produce a failed row.
• Retry attempts and supporting requests do not create extra dataset rows by themselves.
• Nested media, profile information and other arrays remain part of their parent row.
• A normal empty continuation after earlier successes creates no additional row.
• Saved failed rows are not assumed to be free; check their treatment in the active pricing configuration.

More inputs and larger page budgets can produce more saved rows. Start with a small run and check actual usage before increasing the workload.

Pixiv comments API 🔌

Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["149440738"],"pagesPerArtwork":1}'

Download the dataset in JSON, CSV, Excel or other formats available in the Console, or retrieve it through the Apify API. Use schedules, webhooks and Apify integrations to connect results to Google Sheets, Make, Zapier, cloud storage or your own application. These connections are configured separately by the user.

Reliability, retries, and public-data limits ⚠️

Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or unavailable targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors allow up to five total attempts per request.

Successful earlier pages remain saved if a later request fails. A normal end after saved results is not retried. An input with no accessible results can receive a failed row; that alone does not prove that its underlying source does not exist. An exhausted later request can add a failed row while preserving previous output.

Collects root comments only; has_replies signals replies without collecting a complete reply tree. Sticker-only comments can have empty text and a stamp ID. The public artwork is checked first; disabled comments stop before list requests.

Pixiv controls public availability, ranking and optional fields. Result counts can be affected by duplicates, removed content and changes during a run. A page budget is a collection limit, not a promise of exhaustive coverage.

An invalid string within a valid input list does not stop other inputs. Invalid overall configuration, such as a non-string list item or a wrong page-count type, exits before source requests. Startup failures, unavailable dataset storage or an unrecoverable result-save error can still stop the whole run. A failed save is not retried as a new scraping request.

Frequently asked questions ❓

What does one Pixiv Artwork Comments Scraper result represent?

Each successful row represents one comment. The source input is retained, and nested fields stay in the same row.

Which source limits apply?

Collects root comments only; has_replies signals replies without collecting a complete reply tree. Sticker-only comments can have empty text and a stamp ID. The public artwork is checked first; disabled comments stop before list requests.

Does it download media files?

No. Where available, the Actor returns media URLs and metadata within the result row.

Does it require a Pixiv account or personal cookies?

No. You do not need to provide a Pixiv account, password or personal session cookie. Collection uses HTTP without opening a browser.

What happens to invalid or unavailable inputs?

Invalid individual inputs are recorded as failed without a source request. Confirmed missing or unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts per request; other inputs and earlier saved results remain available.

Can I export results or run the same input again?

Yes. Export the default dataset or retrieve it through the Apify API. You can create an Apify schedule and connect completed runs to your own workflow.

Support, responsible use, and related actors 🛟

For a reproducible issue, use the Actor’s Issues tab and provide the run ID, approximate time, a safe public input, expected behavior and actual result. Include the mode or page budget when relevant. Never share access tokens, personal cookies or proxy credentials.

Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.