ImportYeti Trade Intelligence Scraper

Turn public ImportYeti company profiles into analysis-ready company, supplier, and shipment records.

Use company profile URLs or slugs to collect supplier relationships, shipment totals, origins, HS codes, product descriptions, trade lanes, weights, TEU trends, and recent bills of lading.

The actor is designed for repeatable sourcing research and supply-chain monitoring. It uses the public ImportYeti JSON data surface, requires no account, and returns linked records that work in CSV, JSON, Excel, APIs, and data warehouses.

What does ImportYeti Trade Intelligence Scraper do?

The actor extracts three linked record types:

• 🏢 Company profiles
• 🏭 Supplier relationships
• 🚢 Recent shipments

Every row includes a recordType, companySlug, companyName, sourceUrl, and scrapedAt value.

This makes mixed exports easy to filter while preserving joins between companies, suppliers, and shipments.

Who is it for?

Sourcing teams

• Discover established suppliers behind known importers.
• Compare supplier shipment activity.
• Review product descriptions and HS-code categories.

Import and export analysts

• Track shipment, weight, and TEU trends.
• Analyze origin countries and trade lanes.
• Monitor first and latest shipment dates.

Ecommerce operators

• Research supply chains behind retailers and brands.
• Find product and supplier patterns.
• Build recurring competitor intelligence feeds.

B2B researchers

• Enrich company lists with trade evidence.
• Identify active supplier relationships.
• Export structured records to a CRM or warehouse.

Why use this actor?

• ✅ No ImportYeti login or API key required
• ✅ URL and slug inputs
• ✅ Company, supplier, and shipment records
• ✅ Bounded output controls
• ✅ Monthly and quarterly trends
• ✅ HS codes and product descriptions
• ✅ Source URLs on every result
• ✅ Scheduled monitoring on Apify

Data you can extract

Group	Example fields
Company	name, aliases, address, country, website, phone
Trade totals	shipments, first date, latest date, shipping cost
Trends	monthly shipments, weight, TEU, China metrics
Suppliers	name, address, country, shipment share, 12-month volume
Products	descriptions, HS chapters, HS codes
Shipments	bill numbers, date, quantity, weight, TEU
Parties	shipper, consignee, notify party
Provenance	source URL, slug, extraction timestamp

How to use it

1. Open the actor input page.
2. Add one or more ImportYeti company profile URLs.
3. Set supplier and shipment limits.
4. Choose whether to preserve time series and HS-code details.
5. Click Start.
6. Export the dataset in your preferred format.

A low-cost first run can use one company with ten suppliers and ten shipments.

Input

Company profile URLs

Use URLs such as:

https://www.importyeti.com/company/wal-mart

Company slugs

You can also provide the final path segment:

wal-mart

Output limits

• maxSuppliersPerCompany: 0 to 50
• maxShipmentsPerCompany: 0 to 50

Detail options

• includeTimeSeries: preserve monthly and quarterly metrics
• includeHsCodes: preserve HS-code arrays
• requestDelayMs: delay between company requests

Input example

{
  "companyUrls": [
    "https://www.importyeti.com/company/wal-mart"
  ],
  "companySlugs": [],
  "maxSuppliersPerCompany": 10,
  "maxShipmentsPerCompany": 10,
  "includeTimeSeries": true,
  "includeHsCodes": true,
  "requestDelayMs": 500
}

Output

Company example:

{
  "recordType": "company",
  "companySlug": "wal-mart",
  "companyName": "Wal Mart",
  "totalShipments": 690729,
  "countryCode": "US",
  "firstShipmentDate": "01/01/2015",
  "sourceUrl": "https://www.importyeti.com/company/wal-mart"
}

Supplier example:

{
  "recordType": "supplier",
  "companySlug": "wal-mart",
  "supplierName": "Example Supplier",
  "supplierCountryCode": "CN",
  "shipments12Months": 1450,
  "productDescriptions": ["Example product"]
}

Shipment example:

{
  "recordType": "shipment",
  "companySlug": "wal-mart",
  "shipmentDate": "08/07/2026",
  "billOfLading": "EXAMPLE123",
  "originCountry": "Mexico",
  "hsCode": "852872"
}

How much does it cost to scrape ImportYeti trade data?

This actor uses pay-per-event pricing.

• A small start event covers run initialization.
• Each saved dataset record is charged as one item.
• Apify plan tiers receive volume-adjusted item prices.

Your final cost depends on the number of companies and the supplier and shipment limits.

Use smaller limits when testing a workflow.

Sourcing workflow

1. Start with a list of target importer URLs.
2. Extract leading suppliers.
3. Filter suppliers by origin country.
4. Rank relationships by recent shipment activity.
5. Review products and HS chapters.
6. Send shortlisted suppliers to qualification.

Monitoring workflow

Schedule the actor weekly or monthly.

Compare these fields over time:

• shipments12Months
• shipmentsPrevious12Months
• latestShipmentDate
• isNewSupplier
• monthlyTimeSeries
• quarterlyTimeSeries

Store snapshots in Google Sheets, a database, or an Apify integration.

Tips for reliable results

• Copy the canonical public company profile URL.
• Keep the default request delay for large batches.
• Start with one known company before uploading a long list.
• Disable time series when compact payloads matter more than history.
• Use recordType to split rows after export.
• Deduplicate recurring snapshots by company, record type, and entity identifier.

Integrations

Google Sheets

Send scheduled exports to a shared sourcing sheet.

Webhooks

Trigger downstream enrichment when a run finishes.

Zapier and Make

Route new supplier rows into a CRM or review queue.

Data warehouses

Load JSON or CSV exports into BigQuery, Snowflake, or PostgreSQL.

AI analysis

Feed structured trade records to an LLM for supplier summaries and change detection.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/importyeti-trade-intelligence-scraper').call({
  companySlugs: ['wal-mart'],
  maxSuppliersPerCompany: 10,
  maxShipmentsPerCompany: 10
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/importyeti-trade-intelligence-scraper').call(run_input={
    'companySlugs': ['wal-mart'],
    'maxSuppliersPerCompany': 10,
    'maxShipmentsPerCompany': 10,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST \
  'https://api.apify.com/v2/acts/automation-lab~importyeti-trade-intelligence-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"companySlugs":["wal-mart"],"maxSuppliersPerCompany":10,"maxShipmentsPerCompany":10}'

Use with Apify MCP

Connect from Claude Code with the hosted Apify MCP endpoint:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/importyeti-trade-intelligence-scraper"

For Claude Desktop, Cursor, or VS Code, add this server to the client's MCP JSON configuration:

{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=automation-lab/importyeti-trade-intelligence-scraper"
    }
  }
}

The MCP client will prompt you to authenticate with Apify when needed. Example prompts:

• “Extract the leading suppliers for this ImportYeti company URL.”
• “Summarize recent shipment trends and origin countries.”
• “Compare 12-month supplier activity and flag new suppliers.”

Record linking

All records include:

• companySlug
• companyName
• sourceUrl
• scrapedAt

Supplier rows add supplierKey where available.

Shipment rows add bill-of-lading identifiers and supplier URLs where available.

Error handling

Invalid slugs are rejected before requests are made.

Missing companies are logged and skipped so other valid companies can continue.

Transient rate limits and server errors use bounded exponential backoff.

The run fails when no records can be produced.

Legality and responsible use

ImportYeti presents public trade information derived from shipment records.

Use the actor only for lawful purposes.

Respect applicable laws, contractual duties, privacy requirements, and the source website’s terms.

Do not use results for harassment, discrimination, or unlawful profiling.

FAQ

Does this actor require an ImportYeti account?

No. It uses the anonymously accessible public company data surface.

Can I search by arbitrary company name?

Not currently. Use a known company profile URL or slug. This avoids relying on an unproven search endpoint.

Why are there multiple record types?

A company profile contains distinct company, supplier, and shipment facts. recordType keeps one export easy to filter and join.

Why did my run return no data?

Confirm the URL opens a company profile and contains /company/<slug>. Try the slug directly if the URL has tracking parameters.

How can I reduce output size?

Lower supplier and shipment limits, or disable time series and HS-code details.

Can I schedule the actor?

Yes. Use Apify schedules and integrations for recurring supply-chain monitoring.

Related scrapers

Explore other business and lead intelligence tools from automation-lab.

Combine this actor with company enrichment, website technology, email discovery, or business directory actors when building a broader sourcing workflow.

Support

If a public ImportYeti profile works in a browser but fails here, include the profile URL and run ID in an Apify issue.

Avoid sharing confidential downstream data.

We use reproducible run evidence to investigate source changes and extraction problems.