iPROS Scraper - Japan Products & Company Data avatar

iPROS Scraper - Japan Products & Company Data

Pricing

from $2.20 / 1,000 results

Go to Apify Store
iPROS Scraper - Japan Products & Company Data

iPROS Scraper - Japan Products & Company Data

Extract public iPROS product listings, company profiles and rankings for Japan supplier research. Get available business contacts and export structured rows. Pay per delivered row plus a small start fee.

Pricing

from $2.20 / 1,000 results

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

1

Bookmarked

3

Total users

2

Monthly active users

2 days ago

Last modified

Security

Limited permissions

Share

iPROS Scraper

Collect iPROS product listings, company profiles and rankings for Japan supplier research as structured rows you can export.

  • Search industrial products by keyword or category.
  • Find companies by industry, prefecture or district.
  • Read product details, company profiles and company product lists.
  • Get available business phones, addresses, websites and images.
  • Export weekly rankings and a reference category table.
  • Pay for rows received: $3.00 per 1,000 rows on the Free plan, plus a small start fee.

What does iPROS Scraper do?

iPROS Scraper collects public product and company information from www.ipros.com. Use it for supplier shortlists, catalog comparisons and recurring research. It is an unofficial tool, not affiliated with iPROS.

  • Product search and detail: use keyword, categoryId, category2Id, productId or product URLs.
  • Company search and detail: use businessClass, prefecture, district, companyId or company URLs.
  • Company products: choose company_products for separate product rows, not a product array inside a company row.
  • Rankings: choose ranking for products and their displayed weekly positions.
  • Category reference: choose categories for one taxonomy row containing the bundled filter tables, not a live category crawl.

locale accepts en and ja; the default is en. Company details, company product lists and rankings use Japanese pages. Contact enrichment also uses Japanese company profiles, so an English search can contain Japanese company information.

enrichDetails is on by default for product and company searches. It adds available details to existing rows rather than creating separately billed company rows. It does not enrich every row in a large search.

What data can you extract from iPROS?

Every row has rowType, a string id, locale and scrapedAt. Available fields depend on the mode and source page. Examples below illustrate the format; they are not a live sample.

Product rows: product

Used by product search and company product lists.

FieldDescriptionExample
productIdiPROS product identifier2000123456
nameProduct nameIndustrial sensor
urlProduct pagehttps://www.ipros.com/product/detail/2000123456/
companyIdSupplier identifier2099665
companyNameSupplier nameExample Manufacturing Co.
imageProduct image URL, when presenthttps://example.com/sensor.jpg

Product detail rows: product_detail

Include product identifiers plus available detail fields.

FieldDescriptionExample
descriptionProduct descriptionSensor for production equipment
priceRangePrice text shown by iPROSContact supplier
officialSiteUrlOfficial external pagehttps://example.com/
categoryIdFirst-level category identifier100113
category2IdSecond-level category identifier100385

Company rows: company

Search rows may include profile fields when enrichment succeeds.

FieldDescriptionExample
companyIdCompany identifier2099665
nameCompany nameExample Manufacturing Co.
urlCompany pagehttps://www.ipros.com/company/detail/2099665/
businessClassIndustry identifier100077
prefectureRegion identifier13

Company detail rows: company_detail

These fields can also appear on enriched product or company rows.

FieldDescriptionExample
phonesAvailable phone and fax entries[{"value":"+1 555 0100","type":"landline"}]
address.fullFull published business addressExample business address, Tokyo, Japan
geoCoordinates when available{}
orgOrganization name and identifier{"name":"Example Manufacturing Co.","id":"2099665"}
web.websiteCompany websitehttps://example.com/
emailsEmail list; currently empty on these public profiles[]
personNamed contact; currently empty{}
leadAbsencesReasons for missing contact fields{"emails":"本站无"}
businessActivitiesDescription of the company's businessIndustrial equipment supply
productCountTotal stated on the company page, or null25
catalogCountCatalog count4

leadAbsences uses 本站无 for not present and 未验证 for not verified. Missing coordinates are not filled with a guessed location.

Ranking rows: ranking_product

FieldDescriptionExample
productIdRanked product identifier2000123456
rankPosition shown by iPROS; ties can share a rank1
nameRanked product nameIndustrial sensor

Category rows: taxonomy

FieldDescriptionExample
idReference-table identifieripros-taxonomy
productCategoriesProduct category identifiers and labels[{"id":"100113","name":"Logistics Equipment"}]

How to scrape iPROS

  1. Open iPROS Scraper in Apify Console. A free Apify account is enough to try it.
  2. Fill one target field, such as keyword, and leave mode on auto.
  3. Set maxResults to 5 for a small first run.
  4. Click Start and wait for completion.
  5. Download the dataset as JSON, CSV or Excel, or read it through the API.

Empty input starts an example product search for sensor, with locale: "en" and a limit of 3 rows. Normal start and row charges still apply. With a target supplied, automatic mode selection prefers URLs, then IDs, keywords, product categories and company region or industry filters. Choose an explicit mode when the same field serves several purposes.

Fill keyword, categoryId or category2Id. A second-level category narrows the search. Japanese keywords are useful for Japanese catalog terms.

Product detail

Fill productId or supply product detail URLs in startUrls. One product becomes one row with available details and company contact information.

Fill businessClass, prefecture or district. For keyword-based company searches, explicitly set mode to company_search; a keyword alone selects product search.

Company detail

Fill companyId or supply company detail URLs. The row describes the company; use the separate product-list mode to retrieve its products.

Company products

Set mode to company_products and fill companyId or company detail URLs. Products are separate rows with company identifiers and available contact fields.

Rankings

Set mode to ranking. No keyword or identifier is needed. Ranking rows are not a source of enriched company contacts.

Categories

Set mode to categories. No target is needed. The reference covers product categories, company industries and regional filters; it does not prove every category currently has results.

What to fill in

FieldWhat to enterDefault
modeAutomatic selection or one of the seven modes aboveauto
startUrlsProduct or company detail URLs; one search URL can supply its filtersEmpty
keywordOne product or company search phraseEmpty; example sensor
productIdIdentifier from a product detail URLEmpty
companyIdIdentifier from a company detail URLEmpty
categoryIdFirst-level product category, such as 100113Empty
category2IdSecond-level product category, such as 100385Empty
businessClassIndustry, such as 100077 for information and communicationsEmpty
prefectureRegion ID, such as 13 for Tokyo or 27 for OsakaEmpty
districtRegion group, such as 4 for Southern KantoEmpty
localeen or ja; not a translation guaranteeen
maxResultsRow limit per input, from 1 to 5,00070; form prefill 3
enrichDetailsAdd available profile details to search rowstrue

Product search:

{"keyword":"sensor","locale":"ja","maxResults":5}

Product detail:

{"productId":"2000123456","maxResults":1}

Company search:

{"mode":"company_search","prefecture":"13","maxResults":5}

Company detail:

{"companyId":"2099665","maxResults":1}

Company products:

{"mode":"company_products","companyId":"2099665","maxResults":5}

Rankings:

{"mode":"ranking","maxResults":5}

Categories:

{"mode":"categories","maxResults":1}

Use a current product ID from iPROS in place of the illustrative product ID above. Keep each URL list to one page type; do not mix company and product detail URLs.

  • maxItems and limit are aliases for maxResults. query is an alias for keyword.
  • Recognizable misspellings can be corrected; other unknown fields are ignored with a warning. Check the report rather than relying on a misspelling.
  • Missing required targets and invalid row-count values stop the run with INVALID_INPUT: <field> — <how to fix>, before rows are charged. The start fee can still apply.
  • INPUT_REPORT in the default key-value store records fields filled, corrected or ignored and the selected mode. INPUT_ECHO records the parsed settings; RUN_SUMMARY records the outcome and counts. Failures can write ERROR_SUMMARY.

Output example

Illustrative company-detail row, with placeholder contact data:

{
"rowType": "company_detail",
"id": "2099665",
"companyId": "2099665",
"name": "Example Manufacturing Co.",
"url": "https://www.ipros.com/company/detail/2099665/",
"locale": "ja",
"phones": [{"value": "+1 555 0100", "type": "landline"}],
"address": {"full": "Example business address, Tokyo, Japan", "country": "JP"},
"web": {"website": "https://example.com/", "socials": []},
"emails": [],
"person": {},
"leadAbsences": {"emails": "本站无", "person": "本站无"},
"scrapedAt": "2026-10-24T00:00:00+00:00"
}

You can export the dataset as JSON, CSV, Excel, XML, RSS or an HTML table. JSON preserves nested contact fields most directly.

Why use this iPROS scraper?

  • Pay per delivered row. Enriching an existing row does not create a second row charge.
  • Useful identifiers. Product and company IDs let you join results across runs.
  • No invented contacts. Unavailable fields stay empty, with absence reasons where supported.
  • Several pages per run. startUrls accepts a list of detail pages of the same type.
  • Readable input errors. Check the named field and its allowed value before retrying.
  • No proxy setup. You do not need to set up proxies or provide an iPROS account.

Rows already written to the dataset remain available if a run stops. A partial collection may return fewer rows than requested; do not assume an interruption will deliver every row not yet written.

How much does it cost to scrape iPROS?

Pricing is pay per event: an Actor start event costs $0.005, plus the charge for each delivered row. Platform usage is included in these prices.

Apify planPrice per rowPrice per 1,000 rows
Free$0.0030$3.00
Starter$0.0030$3.00
Scale$0.0026$2.60
Business$0.0022$2.20

Platinum and Diamond have the same row price as Business in the Store pricing.

The start event is charged per GB of memory, with a minimum of one event. At the default 512 MB, the start fee is $0.005. For example, one search delivering 50 rows on the Free plan costs 50 × $0.003 + $0.005 = $0.155.

maxResults limits each input: one keyword, search target, ID or start URL. The default is 70; larger requests are collected in parts of up to 70. The run also stops at the Maximum cost per run you set (maxTotalChargeUsd in the API). Free Apify plan users are limited to 200 rows per run and 10 total runs of this Actor. These limits do not make the example run free of charges.

What happens when the run timeout is too short

A short timeout can cause the Actor to pause rather than fail. The run temporarily shows ABORTED, with a message such as "Queued on the collection backend; this run will resume automatically when results are ready (about N s)." The estimate varies with the run.

When results are ready, the same run resumes and writes to the same dataset. Rows already delivered are skipped so they are not delivered or charged twice. A resumed run that has already delivered rows can report "Resumed: delivering N rows." Successful delivery finishes as SUCCEEDED; an actual collection failure can still fail the run.

This pause can happen at most 3 times per run. Keep the default timeout of 3600 seconds to reduce interruptions. Synchronous endpoints (run-sync and run-sync-get-dataset-items) wait at most 300 seconds and can return no rows while a run is paused. For longer jobs, start asynchronously and read the dataset after SUCCEEDED, or use a success webhook.

Use with AI agents and the API

Apify MCP server (Claude, ChatGPT, Cursor, VS Code)

Add this Actor to a client supporting remote MCP servers:

https://mcp.apify.com?tools=lentic_clockss/ipros-scraper

Sign in with Apify through OAuth, or send Authorization: Bearer <YOUR_APIFY_TOKEN>. The tool starts a run and returns run and dataset IDs; the agent can read rows with get-dataset-items.

Clients without remote support can use npx @apify/actors-mcp-server --tools lentic_clockss/ipros-scraper with APIFY_TOKEN set.

Example prompt: "Find five iPROS companies in Tokyo using company_search and prefecture 13. Return names, websites and available business phones."

Apify API

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("lentic_clockss/ipros-scraper").call(
run_input={"mode": "company_search", "prefecture": "13", "maxResults": 5}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('lentic_clockss/ipros-scraper').call({
mode: 'company_search', prefecture: '13', maxResults: 5
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

For asynchronous HTTP calls, send the input JSON to POST https://api.apify.com/v2/acts/lentic_clockss~ipros-scraper/runs with an Authorization: Bearer header. Read results using GET https://api.apify.com/v2/datasets/<datasetId>/items?format=json after completion.

Integrations

Use the Integrations tab to connect results to Google Sheets, Make, Zapier, n8n, Slack, Airtable or a webhook. Use Apify Schedules for recurring runs.

日本語の説明

iPROS の公開製品情報、企業プロフィール、製品ランキングを行単位で取得できます。製品を探す場合は keyword またはカテゴリ番号を入力し、企業を探す場合は prefecture や businessClass を指定してください。最初は maxResults を三件から五件にすると、出力を確認しやすくなります。企業詳細や連絡先には日本語の情報を使用します。電話番号や住所は公開されている場合のみ取得し、掲載のないメールアドレスや担当者名は補いません。料金は開始時の少額料金と、実際に出力された行数で決まります。カテゴリ一覧は参考用の収録データで、毎回更新される一覧ではありません。

FAQ

This Actor collects public information. You are responsible for checking iPROS terms and applicable data-protection law. Processing personal data requires a lawful basis; public visibility alone is not permission for every use.

Why did my run end as ABORTED?

Read its status message. The automatic pause described above can temporarily show ABORTED before resuming. A manual abort is different and does not promise automatic recovery.

How many results can I get?

maxResults accepts 1–5,000 per input, subject to available results, your spending limit and free-plan limits. A detail page normally produces one row; categories produces one reference row.

Why are some fields empty?

iPROS may not publish them, or enrichment may not succeed. Public company profiles currently yield empty emails and person fields. Check leadAbsences and RUN_SUMMARY rather than treating missing data as a verified negative.

Does enrichment cover every search result?

No. Product search attempts detail enrichment for up to 10 rows per search, and company search for up to 8. Larger searches retain simpler rows beyond that limit. Use detail mode for a specific page.

Does English mode translate company addresses?

No. Company profiles and contact enrichment use Japanese information to preserve the published address. locale: "en" is not a promise that all output fields will be English.

Can I download catalogs or submit inquiries?

No. Catalog references may appear, but the Actor does not log in, submit inquiry forms or download gated catalog files.

Is this an official iPROS API?

No. It is an independent scraper. Report missing fields or parsing problems through the Actor's Issues tab.

Limitations

  • Public iPROS pages only; private accounts and inquiry forms are outside the scope.
  • Rankings use Japanese pages and do not add company-contact enrichment.
  • Category reference data can lag behind changes on iPROS.
  • Search results and field availability can change; the requested row count is a ceiling, not a guarantee.
  • Company rows omit embedded product previews. Use company_products for product rows.
  • Contact, catalog and industry arrays are limited to 50 entries; count fields indicate truncation where available.
  • No complete coverage claim is made for every industry, category, region or English keyword.

More B2B supplier and wholesale marketplace scrapers from the same publisher:

Browse all of our scrapers at apify.com/lentic_clockss.

Support

Found a problem or need another field? Open an issue in the Issues tab of this Actor's page and include the run ID and the input you used.