/marinetraffic/companies/search

POST /api/marinetraffic/companies/search

Price: 5 credits

Search the MarineTraffic maritime business directory by company name or browse by business sector

How to use it

Find MarineTraffic maritime companies either by name (set keyword) or by browsing a business sector (set sector). Name search returns matching companies with their profile ID, name and trading name. Sector browse returns richer cards: profile ID, name, sector, tagline, website, city, country and logo. Pass the resulting company ID to the companies endpoint for the full profile. Use count to cap how many companies are returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Maximum number of companies to return (min: 1)
• keyword string nullable — Company name to search for (minLength: 1)
• sector string nullable — Browse companies by maritime business sector (one of: "Agriculture", "Automotive", "Aviation", "Brokerage", "Bunker & Oil Supplies", "Cargo Shippers", "Charterers", "Chartering", "Charts", "Chemicals", "Classification Societies / Flag States", "Cleaning Services", "Coast Guard", "Commodity Trading", "Construction", "Container Sales and Trading", "Crewing Services", "Diving and Underwater Services", "Dredging", "Education / Research / Consultancy", "Electronics", "Energy", "Engine Builders", "Environmental / NGO", "Fishing", "Flag Administration", "Freight Forwarder", "Fresh Water Supply", "Government / Military", "Healthcare", "Heavy Lifting", "Hydrographic Services", "Information Technology", "Insurance / Finance / Legal", "Legal Services", "Logistics / Transport / Freight", "Manufacturing", "Marina", "Marine Equipment Suppliers", "Medical", "Metals and Mining", "Offshore Services", "Oil and Gas", "Other", "P&I Clubs & Correspondents", "Pilots", "Port / Terminal Services", "Port Agents", "Port Authorities", "Port Police", "Publications", "Real Estate", "Retail and Consumer", "Sale and Purchase", "Search and Rescue", "Security", "Ship Breakers", "Ship Builders / Engineering", "Ship Chandlers", "Ship Owners / Managers / Operators", "Ship Repairs", "Ship Services / Suppliers", "Ship Tracking", "Shipping Lines", "Software / Technology", "Sports", "Surveyors", "Taxi", "Telecommunications", "Tourism & Hospitality", "Towage & Salvage", "Transportation", "Travel / Entertainment", "Underwater Cable Operators", "Warehousing", "Waste Disposal", "Weather & Routing Services", "Yacht & Pleasure Craft Builders", "Yacht Chartering", "Yacht Equipment")

Response

• @type string (default: "MarinetrafficCompanySearchResult")
• id string required
• name string required
• trading_name string nullable
• sector string nullable
• tagline string nullable
• website_url string nullable
• city string nullable
• country string nullable
• image string nullable
• url string required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.