logo
languageENdown
menu

Rakuten Product Listing Scraper

Collect data from Rakuten Product Listing Scraper.

Data collectionE-commerce & RetailGeneral WebProducts

Overview

What this app does

Collect public data from Rakuten Product Listing Scraper.

Notes

  • Data is collected from Octoparse public crawling endpoints.
  • This app is rate-limited by upstream platform responses and pagination.

Scope and boundaries

Each run uses the template 'rakuten-product-listing-scraper' with validated input schema constraints.

  • Good for
  • Use this app when you need public data from the corresponding source template.
  • Do not use for
  • Do not use it for login-only, private, or inaccessible data that is not publicly visible.

Failure handling

Failure and retry behavior declared by the author. We recommend including it in your system prompt when integrating.

  1. 1Retry failed runs with smaller input scope. If repeated failures continue, verify input format and retry later.

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

FieldBusiness nameTypeRequiredDefaultEnum / ConstraintsExampleDescription
uRLsURLs (up to 1,000)array<string>Yes——["https://search.rakuten.co.jp/search/mall/SKII/"]URLs (up to 1,000)
pageSizePageSizestringNo——PageSizePageSize

Output

Field structure of a single record, generated from the output.schema in manifest.json.

FieldBusiness nameTypeExampleDescription
fieldポイントstring—
field_2送料string—
uRLランキング入賞URLstring—
uRL_2店舗URLstring—
iD商品IDstring—
iD_2店舗IDstring—

Record schema

Output is returned record by record. detail.output.idFieldHint

output.schema
{
  "type": "object",
  "properties": {
    "field": {
      "type": "string",
      "title": "ポイント",
      "prefill": ""
    },
    "field_2": {
      "type": "string",
      "title": "送料",
      "prefill": ""
    },
    "uRL": {
      "type": "string",
      "title": "ランキング入賞URL",
      "prefill": ""
    },
    "uRL_2": {
      "type": "string",
      "title": "店舗URL",
      "prefill": ""
    },
    "iD": {
      "type": "string",
      "title": "商品ID",
      "prefill": ""
    },
    "iD_2": {
      "type": "string",
      "title": "店舗ID",
      "prefill": ""
    }
  },
  "required": [],
  "additionalProperties": false
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "YiJacobJohnRaku__rakuten-product-listing-scraper": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/rakuten-product-listing-scraper",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
View my API Keys →

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

returned record

Charged by the number of records successfully returned. Failed runs are not charged.

Free

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
Please fill in the required parameters first
Free