Extract the shipper, consignee, carrier, vessel and voyage, ports, containers, and cargo lines from a sea waybill — the non-negotiable ocean transport doc.
The full guide: Sea waybill fields, and why it is not a document of title
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
A sea waybill is the non-negotiable ocean transport document that evidences the contract of carriage and receipt of the goods. Unlike a bill of lading, it is not a document of title and does not need to be surrendered at destination — the named consignee takes delivery on proof of identity — so it is faster to release and cannot be endorsed to a third party. This tool is tuned for that document; use the bill of lading extractor for a negotiable B/L.
A sea waybill covers ocean carriage by vessel, so it reads maritime fields — the vessel name, voyage number, ports of loading and discharge, and container and seal numbers. An air waybill covers air transport (airports, flights) and a road waybill or CMR covers road transport (vehicle plate, road route); those have their own extractors linked below.
The document number and date, the booking reference, the shipper, consignee, and notify party with their addresses, the carrier name, and the routing: place of receipt, port of loading, port of discharge, and place of delivery, plus the vessel name and voyage number.
Yes. The containers table returns each container number, type, seal number, package count, and gross mass, and the cargo lines table returns each line with its description, marks and numbers, number and kind of packages, package type, gross mass, measurement, and HS commodity code, so a multi-container consignment comes back as rows alongside the freight and charges and their currency.
PDF only, up to 10MB and 100 pages. The sea waybill is processed via the Talonic API for extraction, is not retained for training, and is not shared.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for freight and customs teams, or the extraction API if you are building it in.