Extract public ImportYeti company and supplier search results for sourcing, lead generation, and trade intelligence workflows.
Use this Actor to turn ImportYeti searches into structured CSV, JSON, Excel, API, or webhook-ready records with shipment counts, addresses, countries, recency signals, and source URLs.
Who is this for?
- Sourcing teams looking for supplier and importer signals from public customs data.
- Private-label and ecommerce sellers researching brands, suppliers, and shipment volume.
- Import/export sales teams building targeted lead lists from trade activity.
- Freight and logistics analysts monitoring company and supplier shipment recency.
- Market researchers comparing public ImportYeti entity records across keywords.
At a glance
- Primary job: Search ImportYeti for public company and supplier records.
- Input: Enter a keyword such as a brand, supplier, product, or company name.
- Output: One dataset row per public ImportYeti result.
- Best for: Supplier discovery, import/export sales, private-label sourcing, logistics research, and recurring market monitoring.
Common use cases
- Supplier discovery: Search a product or brand keyword and export companies, suppliers, shipment counts, addresses, and ImportYeti URLs.
- Lead qualification: Use
minShipmentsto focus on entities with meaningful shipment activity. - Competitor supply-chain monitoring: Schedule repeat runs for brand queries and compare shipment recency over time.
- Workflow automation: Send dataset results to a CRM, spreadsheet, warehouse, or enrichment workflow with Apify integrations.
Input recipes
- Small smoke test:
query="nike",maxItems=10. - Supplier discovery:
query="electronics",minShipments=50,maxItems=25. - Recent supplier leads:
query="apparel",type="supplier",mostRecentShipment="last_24_months".
What data can you extract?
| Field | Description |
|---|---|
query |
Search keyword used for the run. |
searchType |
ImportYeti search mode (companies in v1). |
entityName |
Company or supplier name. |
entityType |
ImportYeti result type, such as company or supplier. |
sourceUrl |
Public ImportYeti result/profile URL. |
country |
Country code shown by ImportYeti. |
address |
Public address shown in search results. |
totalShipments |
Total shipment count shown by ImportYeti. |
mostRecentShipment |
Most recent shipment date shown by ImportYeti. |
otherAddressesCount |
Count of additional known addresses when visible. |
otherNamesCount |
Count of additional known names when visible. |
topSuppliers, topCustomers, hsCodes |
Reserved arrays for future profile-detail expansion. |
status, error |
Per-record status fields. |
Example input
{
"query": "nike",
"searchType": "companies",
"type": "any",
"mostRecentShipment": "any",
"minShipments": 0,
"maxItems": 10,
"proxyConfiguration": { "useApifyProxy": false }
}
Example output
{
"query": "nike",
"searchType": "companies",
"entityName": "Nike Usa",
"entityType": "company",
"sourceUrl": "https://www.importyeti.com/company/nike-usa",
"country": "US",
"address": "Beaverton, Or 97005, Us",
"totalShipments": 139845,
"mostRecentShipment": "11/07/2026",
"topSuppliers": [],
"topCustomers": [],
"hsCodes": [],
"shipmentCount12m": null,
"otherAddressesCount": 37,
"otherNamesCount": 24,
"scrapedAt": "2026-07-15T08:00:00.000Z",
"status": "ok",
"error": null
}
Tips for best results
- Start small: Use
maxItems: 10until you confirm the query returns the right market segment. - Use focused keywords: Brand, supplier, or product terms usually produce cleaner results than broad industry words.
- Avoid empty-success assumptions: The Actor fails when ImportYeti returns no usable records after filters.
- Respect public data boundaries: This Actor extracts public ImportYeti search data only; it does not use private accounts, cookies, or paid ImportYeti API credentials.
API usage
Node.js:
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/importyeti-scraper').call({
query: 'nike',
maxItems: 10,
});
console.log(run.defaultDatasetId);
Python:
from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('fetch_cat/importyeti-scraper').call(run_input={
'query': 'nike',
'maxItems': 10,
})
print(run['defaultDatasetId'])
cURL:
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~importyeti-scraper/runs?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"query":"nike","maxItems":10}'
MCP and AI agents
You can use this Actor from AI agents through Apify MCP or the Apify API. Add the Apify MCP server to Claude CLI:
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors fetch_cat/importyeti-scraper
Example MCP configuration:
{
"mcpServers": {
"apify": {
"command": "npx",
"args": ["-y", "@apify/actors-mcp-server", "--actors", "fetch_cat/importyeti-scraper"],
"env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
}
}
}
Example prompts showing MCP usage for AI agents:
- Supplier research: "Use ImportYeti Scraper to find supplier records for electronics with more than 50 shipments. Return entity name, source URL, and shipment count."
- Brand monitoring: "Run ImportYeti Scraper for Nike with 25 results and summarize companies with the newest shipment dates."
- CRM enrichment: "Search ImportYeti for apparel suppliers, then format the results as CRM leads with
entityName,sourceUrl, andtotalShipments."
Typical agent workflows include CRM enrichment, recurring monitoring, and sourcing research where an agent compares new shipment recency values with earlier datasets.
Responsible use
ImportYeti Scraper collects public search-result data only. Do not use it for private accounts, login-only data, paid ImportYeti API credentials, or contact enrichment that is not visible in public ImportYeti records. Check that your use complies with ImportYeti terms and applicable laws.
Support
If you see blocked pages, missing fields, or a query that should return public ImportYeti results but does not, open an issue from the Actor page and include:
- Input JSON used for the run.
- Expected output you thought should be returned.
- Actual output or error message.
- Reproducible public URL from ImportYeti when possible.
- Run ID so the logs and dataset can be inspected.