Pixiv Profile Scraper avatar

Pixiv Profile Scraper

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Pixiv Profile Scraper

Pixiv Profile Scraper

Extract public Pixiv creator profiles by ID or URL. Export descriptions, avatars, public links, available region details and workspace information.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

ScrapingMonkey

ScrapingMonkey

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Pixiv Profile Scraper — Extract public Pixiv creator profiles by ID or URL. Export descriptions, avatars, public links, available region details and workspace information. Add supported inputs and start a run to get structured public data without providing a Pixiv account.

Export a public Pixiv creator profile with biography, website and available social links. Keep optional workspace information in the same profile record.

At a glanceDetails
📥 InputPositive Pixiv user IDs or public /users/ID profile URLs.
📤 OutputOne profile per success row, with source input retained
📄 PaginationOne lookup per unique input; nested values stay in that result row.
🔐 Login requiredNo
⚡ ProcessingUp to 5 HTTP requests concurrently with automatic retries
💾 DeliveryOne Apify dataset view, useful flat columns and complete nested JSON

What the pixiv profile scraper collects 📊

Extract public Pixiv creator profiles by ID or URL. Export descriptions, avatars, public links, available region details and workspace information.

Data can include:

  • Source identity and public links
  • Available id, url, name, description, description html, avatar url, background url, website url
  • Original input retained with every result
  • One consistent success or failed record format

How to collect profiles from Pixiv 🚀

  1. Enter one or more supported inputs in inputList.
  2. Review the supported input format.
  3. Start the Actor.
  4. Open the Profiles dataset view and review the individual records.
  5. Export the dataset or retrieve it from your application.
{
"inputList": [
"11211325"
]
}

One lookup per unique input; nested values stay in that result row.

Pixiv profiles data and complete output 📦

FieldTypeMeaning
statusstringResult status: success or failed.
inputstringOriginal submitted input.
idstring or nullStable ID of the result entity, retained as a string.
urlstring or nullPublic source URL of the result entity.
namestring or nullPublic name supplied by the source.
descriptionstring or nullPublic description in plain text when exposed by this endpoint.
description_htmlstring or nullPublic description in the HTML format returned by Pixiv.
avatar_urlstring or nullAvailable avatar URL.
background_urlstring or nullAvailable background URL.
website_urlstring or nullAvailable website URL.
is_premiumboolean or nullIs premium when exposed by the public response.
is_officialboolean or nullIs official when exposed by the public response.
following_countinteger or nullPublic count of accounts this creator follows, not the number of their followers.
mypixiv_countinteger or nullPublic My pixiv relationship count when supplied.
region_namestring or nullRegion name when exposed by the public response.
region_codestring or nullRegion code when exposed by the public response.
jobstring or nullJob when exposed by the public response.
social_linksarray or nullSocial links when exposed by the public response.
social_links[].servicestring or nullService when exposed by the public response.
social_links[].urlstring or nullPublic source URL.
workspacearray or nullOptional creator-published workspace fields; each entry retains the source field name.
workspace[].fieldstring or nullField when exposed by the public response.
workspace[].valuestring or nullValue 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": "11211325",
"id": "11211325",
"url": "https://www.pixiv.net/en/users/11211325",
"name": "CORE",
"description": "心温まるかわいいものが好きです('ω')\r\n時間の合間を盗んでは気楽に描いてます、\r\nマイピク・フォローなどどなたでもよろしくお願いします^^\r\n\r\n※既に趣味の領域で気楽に描いてるので、金銭の絡むお仕事イラストはただいま一切受け付けておりません",
"description_html": "心温まるかわいいものが好きです(&#39;ω&#39;)<br />時間の合間を盗んでは気楽に描いてます、<br />マイピク・フォローなどどなたでもよろしくお願いします^^<br /><br />※既に趣味の領域で気楽に描いてるので、金銭の絡むお仕事イラストはただいま一切受け付けておりません",
"avatar_url": "https://i.pximg.net/user-profile/img/2014/06/08/21/12/00/7969430_f567285b2bfdd405bb0691d73e8624c0_170.jpg",
"background_url": null,
"website_url": null,
"is_premium": true,
"is_official": false,
"following_count": 457,
"mypixiv_count": 55,
"region_name": "Japan",
"region_code": "JP",
"job": null,
"social_links": [
{
"service": "twitter",
"url": "https://twitter.com/daddymulk2013"
}
],
"workspace": [
{
"field": "userWorkspacePc",
"value": "pixivすら重い"
},
{
"field": "userWorkspaceMonitor",
"value": "この前溶けた"
},
{
"field": "userWorkspaceTool",
"value": "エラーに悩まされてる"
}
]
}

Complete failed result:

{
"status": "failed",
"input": "invalid input",
"id": null,
"url": null,
"name": null,
"description": null,
"description_html": null,
"avatar_url": null,
"background_url": null,
"website_url": null,
"is_premium": null,
"is_official": null,
"following_count": null,
"mypixiv_count": null,
"region_name": null,
"region_code": null,
"job": null,
"social_links": null,
"workspace": 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 Profiles view; arrays are not expanded into extra result rows.

Input requirements and pagination settings ⚙️

ParameterTypeRequiredDefaultRules
inputListarray of stringsYesNonePositive Pixiv user IDs or public /users/ID profile URLs. At least 1 item.

Positive Pixiv user IDs or public /users/ID profile URLs.

Examples of supported inputs: 11211325.

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.

There is no result-page setting. Each unique target is looked up individually, and nested fields remain within that result row.

Pixiv profiles use cases 🎯

Enrich a Pixiv creator profile

Export a public Pixiv creator profile with biography, website and available social links. Keep optional workspace information in the same profile record.

Collect selected public Pixiv profiles and their available website and social links. Build a source directory for manual creator research from the export.

Review public Pixiv creative workspace details

Collect a Pixiv creator profile with any publicly supplied workspace fields, biography and job information. Optional fields remain null when absent.

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 profile 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 can produce more saved rows. Start with a small run and check actual usage before increasing the workload.

Pixiv profiles 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":["11211325"]}'

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.

Follower counts are not exposed by the verified public response. Following count is a different metric. Region, job, workspace and social links are optional and can be absent. No private profile data is requested.

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 Profile Scraper result represent?

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

Which source limits apply?

Follower counts are not exposed by the verified public response. Following count is a different metric. Region, job, workspace and social links are optional and can be absent. No private profile data is requested.

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.

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.