Bill Of Lading Scraper
Pricing
from $3.99 / 1,000 results
Bill Of Lading Scraper
Public-page metadata extraction Actor for the inventory entry Bill Of Lading Scraper.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
a month ago
Last modified
Categories
Features
Share
What does the Bill of Lading Scraper do?
This Actor reads public ImportYeti company or shipment pages and extracts explicitly published bill-of-lading records. It can normalize BOL number, bill type, master BOL number, arrival and departure dates, importer/company, supplier, notify party, origin and destination ports, public geocodes, commodity description, and container IDs/descriptions when those values are present in public page data.
The Actor uses bounded public HTTPS requests and may use an optional standard Apify Proxy route. It does not call a paid ImportYeti API, require login, infer shipment values, solve CAPTCHAs, or bypass authentication, paywalls, robots restrictions, or anti-bot challenges. If the source presents a challenge or does not publish explicit BOL data, the run emits a typed diagnostic row and records the result in OUTPUT_SUMMARY.
Why use the Bill of Lading Scraper?
ImportYeti’s public site provides company search and public customs-shipment context. A normalized BOL row keeps the public supply-chain fields together while retaining the source page for review. The parser accepts public JSON-LD, embedded JSON, Next data, and visible BOL-number text, removes duplicates, and never fabricates a shipment.
How to use the Bill of Lading Scraper
Provide startUrls with public ImportYeti company or shipment pages, or provide companyNames to build public company paths. maxPages bounds pages and maxItems bounds records. timeoutSecs, requestDelayMillis, and maxRetries bound direct request work.
For deterministic local validation, set fixturePath to the supplied HTML fixture. Fixture mode uses the same parser, normalization, validation, and output path without contacting ImportYeti. The run summary also records request, retry, page, filtering, and data-availability counters.
Input
{"startUrls": [{"url": "https://www.importyeti.com/company/example"}],"maxPages": 1,"maxItems": 2,"timeoutSecs": 45,"requestDelayMillis": 500,"maxRetries": 1}
Only public HTTPS importyeti.com URLs are accepted. maxPages is a total page budget across the supplied start URLs and explicit rel="next" links; maxItems is a global record cap. Fixture paths must be repository-relative HTML or JSON files and cannot escape the Actor directory. proxyConfiguration selects only the standard Apify Proxy route; proxy use remains transparent and fail-closed.
Output
Normal rows contain public BOL fields plus sourceUrl, sourceDomain, searchUrl, pageNum, and scrapedAt. Diagnostics contain recordType: "diagnostic", diagnosticType, source URL/domain, error, errorCode, and scrapedAt; inventory metadata, evidence dumps, transport labels, and debug payloads are not emitted in dataset rows.
Example:
{"bolNumber": "MAEU123456789","companyName": "Example Importer","supplierName": "Example Supplier","arrivalDate": "2026-08-15","destinationPort": "Los Angeles","commodityDescription": "Vehicle parts","sourceUrl": "https://www.importyeti.com/company/example","sourceDomain": "www.importyeti.com","scrapedAt": "2026-09-10T00:00:00.000Z"}
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data table
| Field | Meaning |
|---|---|
bolNumber, masterBolNumber, billType | Public shipment identity. |
companyName, supplierName, notifyPartyName | Public shipment parties. |
arrivalDate, departureDate, originPort, destinationPort | Public movement context. |
commodityDescription, containerCount, containerIds | Public cargo/container fields. |
sourceUrl, sourceDomain, searchUrl, pageNum, scrapedAt | Public source provenance and observation time. |
url, error, errorCode, diagnosticType | Typed diagnostic fields when unavailable. |
How much does it cost to scrape ImportYeti?
Local fixture validation uses local compute only. A deployed run’s cost depends on direct request time, page count, and dataset size under the selected Apify plan. Keep limits, delays, timeouts, and retries bounded for predictable work.
Tips or Advanced options
Start with one public company page and a small maxItems. Use a modest delay for multiple pages. SOURCE_CHALLENGE is an honest source result; increasing retries does not bypass a challenge.
FAQ, disclaimers, and support
Public customs data can change, be delayed, or disappear. The Actor reports only fields present in the public response and does not guarantee completeness, legal provenance, ownership, or accuracy. Check ImportYeti terms and robots guidance and follow applicable privacy, compliance, and data-use laws. Use the project Issues tab for feedback or authorized integration requests.
Local validation
npm installnode --test test/public-contract.test.jsapify validate-schemaapify run --purge --input-file test/inputs/fixture.jsonnode validate-datasets.js