# Niconico User Details Scraper (`scrapingmonkey/niconico-user-details-scraper`) Actor

Extract public Niconico creator profiles with biographies, follower and following counts, profile images, account level, and social links.

- **URL**: https://apify.com/scrapingmonkey/niconico-user-details-scraper.md
- **Developed by:** [ScrapingMonkey](https://apify.com/scrapingmonkey) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**Niconico User Details Scraper** — Extract public Niconico creator profiles with biographies, follower and following counts, profile images, account level, and social links. Add supported inputs and start a run to get structured public data without providing a Niconico account.

Export a public Niconico creator profile with biography, available social links and follow counts to create a source-linked account reference record.

| At a glance | Details |
|---|---|
| 📥 Input | Enter positive numeric Niconico user IDs or public user URLs. A user video or mylist tab URL also identifies its user. |
| 📤 Output | One user per success row, with source input retained |
| 📄 Pagination | One lookup per unique input; nested values stay in that result row. |
| 🔐 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 niconico user details scraper collects 📊

Extract public Niconico creator profiles with biographies, follower and following counts, profile images, account level, and social links.

Data can include:

- Source identity and public links
- Available id, url, nickname, description, description text, icon small url, icon large url, is premium
- Original input retained with every result
- One consistent success or failed record format

### How to collect users from Niconico 🚀

1. Enter one or more supported inputs in `inputList`.
2. Review the supported input format.
3. Start the Actor.
4. Open the **Users** dataset view and review the individual records.
5. Export the dataset or retrieve it from your application.

```json
{
  "inputList": [
    "https://www.nicovideo.jp/user/1"
  ]
}
```

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

### Niconico users data and complete output 📦

| Field | Type | Meaning |
|---|---|---|
| `input` | string | Original submitted input. |
| `status` | string | Result status: success or failed. |
| `type` | string or null | Entity type of this row. |
| `id` | string or null | Stable public entity ID, exported as text. |
| `url` | string or null | Public page URL for this entity. |
| `nickname` | string or null | Public user display name. |
| `description` | string or null | Source description. May contain markup. |
| `description_text` | string or null | Plain-text profile description returned by the source. |
| `icon_small_url` | string or null | Small profile image URL. |
| `icon_large_url` | string or null | Large profile image URL. |
| `is_premium` | boolean or null | Profile premium-status flag returned by the source. |
| `follower_count` | integer or null | Public follower count for the profile or mylist. |
| `following_count` | integer or null | Number of accounts the profile follows. |
| `registered_version` | string or null | Niconico version label associated with registration. |
| `level` | integer or null | Current public user level. |
| `level_experience` | integer or null | Current level experience reported by the source. |
| `next_level_experience` | integer or null | Next-level experience value reported by the source. |
| `next_level_threshold_experience` | integer or null | Next-level threshold experience reported by the source. |
| `is_activity_readable` | boolean or null | Source flag indicating whether the public activity feed is readable. |
| `social_links` | array or null | Public social links from the profile. |
| `social_links[].type` | string or null | Type when exposed by the public response. |
| `social_links[].label` | string or null | Label when exposed by the public response. |
| `social_links[].screen_name` | string or null | Screen name when exposed by the public response. |
| `social_links[].url` | string or null | Public source URL. |
| `social_links[].icon_url` | string or null | Available icon URL. |
| `cover_image_url` | string or null | Public profile cover image URL, if present. |

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):

```json
{
  "input": "https://www.nicovideo.jp/user/1",
  "status": "success",
  "type": "user",
  "id": "1",
  "url": "https://www.nicovideo.jp/user/1",
  "nickname": "shinno",
  "description": "",
  "description_text": "",
  "icon_small_url": "https://secure-dcdn.cdn.nimg.jp/nicoaccount/usericon/0/1.jpg?1671282761",
  "icon_large_url": "https://secure-dcdn.cdn.nimg.jp/nicoaccount/usericon/0/1.jpg?1671282761",
  "is_premium": false,
  "follower_count": 1569,
  "following_count": 0,
  "registered_version": "(β)",
  "level": 33,
  "level_experience": 2728,
  "next_level_experience": 54700,
  "next_level_threshold_experience": 4600,
  "is_activity_readable": true,
  "social_links": [
    {
      "type": "twitter",
      "label": "X",
      "screen_name": "shinno",
      "url": "https://x.com/shinno",
      "icon_url": "https://resource.video.nimg.jp/web/images/sns_icon/x_sns.png"
    },
    {
      "type": "facebook",
      "label": "Facebook",
      "screen_name": "shinnosuke.suzuki",
      "url": "https://www.facebook.com/shinnosuke.suzuki",
      "icon_url": "https://resource.video.nimg.jp/web/images/sns_icon/facebook.png"
    },
    {
      "type": "instagram",
      "label": "Instagram",
      "screen_name": "shinno.s",
      "url": "https://www.instagram.com/shinno.s",
      "icon_url": "https://resource.video.nimg.jp/web/images/sns_icon/instagram.png"
    }
  ],
  "cover_image_url": null
}
```

Complete failed result:

```json
{
  "input": "invalid input",
  "status": "failed",
  "type": null,
  "id": null,
  "url": null,
  "nickname": null,
  "description": null,
  "description_text": null,
  "icon_small_url": null,
  "icon_large_url": null,
  "is_premium": null,
  "follower_count": null,
  "following_count": null,
  "registered_version": null,
  "level": null,
  "level_experience": null,
  "next_level_experience": null,
  "next_level_threshold_experience": null,
  "is_activity_readable": null,
  "social_links": null,
  "cover_image_url": 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 Niconico does not supply them. Object fields are exposed through useful columns in the single **Users** 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 | Enter positive numeric Niconico user IDs or public user URLs. A user video or mylist tab URL also identifies its user. At least `1` item. |

Enter positive numeric Niconico user IDs or public user URLs. A user video or mylist tab URL also identifies its user.

Examples of supported inputs: `https://www.nicovideo.jp/user/1`.

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.

### Niconico users use cases 🎯

#### Inspect a Niconico creator profile

Export a public Niconico creator profile with biography, available social links and follow counts to create a source-linked account reference record.

#### Research a Niconico gaming creator profile

Collect a Niconico gaming creator's public biography, profile images, follow counts and account metrics to prepare a creator research brief.

#### Research a Niconico music creator profile

Export a Niconico music creator's public profile, including biography, available social links and follow counts, for a source-linked creator directory.

### 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 user 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.

### Niconico users API 🔌

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

```bash
curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["https://www.nicovideo.jp/user/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.

Follower and following counts are summary metrics, not lists of accounts. Account level and experience are raw profile metrics; no audience estimates are inferred.

Niconico 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 Niconico User Details Scraper result represent?

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

#### Which source limits apply?

Follower and following counts are summary metrics, not lists of accounts. Account level and experience are raw profile metrics; no audience estimates are inferred.

#### Does it download media files?

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

#### Does it require a Niconico account or personal cookies?

No. You do not need to provide a Niconico 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.

# Actor input Schema

## `inputList` (type: `array`):

Enter positive numeric Niconico user IDs or public user URLs. A user video or mylist tab URL also identifies its user.

## Actor input object example

```json
{
  "inputList": [
    "https://www.nicovideo.jp/user/1"
  ]
}
```

# Actor output Schema

## `users` (type: `string`):

One dataset row per public user. Check success or failed status.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "inputList": [
        "https://www.nicovideo.jp/user/1"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapingmonkey/niconico-user-details-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "inputList": ["https://www.nicovideo.jp/user/1"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapingmonkey/niconico-user-details-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "inputList": [
    "https://www.nicovideo.jp/user/1"
  ]
}' |
apify call scrapingmonkey/niconico-user-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapingmonkey/niconico-user-details-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1YgIokqldX7asSoNH/builds/SCIDwbsCHLZsPsH0D/openapi.json