Dockflow

Search for containers by container number. Searches across all tradeflows the user has access to. Admin users can see all containers across all entities. Note: The same container can appear multiple times if it's linked to multiple tradeflows. TIMES ARE LOCAL TO THE PLACE THE EVENT HAPPENED, and every datetime carries that place's UTC offset. A discharge at Antwerp reads ``+02:00``, a pick-up at Altamira reads ``-06:00``. Report the time exactly as given: do NOT convert it to UTC, to your own timezone, or to the reader's, and never restate it as "UTC". Name the place or its zone next to the time, e.g. "loaded 09:36 local time at Gebze (UTC+3)". Mind the date as well as the clock. An event at 03:01 UTC in Altamira is 21:01 on the PREVIOUS DAY locally, so quote the date the value carries rather than the one a UTC reading would imply. Args: query: Container number, or at least its first 4 characters limit: Maximum number of results to return (default: 50, 1 to 100) Returns: ``{"results": [...]}`` - an object with a ``results`` array of matching containers, each with comprehensive info: - container_number: Full container number - container_type / container_type_group: ISO size-type, e.g. "45G1" - tradeflow_id: Associated tradeflow ID - tradeflow_reference: Tradeflow reference number (entity-specific) - url: Deep link to the container's tradeflow in the Dockflow app - pol_name / pod_name: Port of loading / final port of discharge - pol_timezone / pod_timezone: IANA zone of those ports - etd_pol / eta_pod: estimated vessel departure (POL) / arrival (POD) from the carrier schedule, in that port's local time. These are ESTIMATES, not confirmations. Actual vs predicted milestone dates, each in the local time of the place that milestone happened. An ``actual_*`` value means the event has already happened; a ``predicted_*`` value is the currently expected date and may still change. Either may be null: - actual_empty_dispatched_at / predicted_empty_dispatched_at - actual_gated_in_at / predicted_gated_in_at - actual_loaded_at / predicted_loaded_at: loaded on board at POL - actual_departed_at / predicted_departed_at: vessel departure - actual_arrived_at / predicted_arrived_at: vessel arrival - actual_discharged_at / predicted_discharged_at: unloaded at POD - actual_gate_out_at / predicted_gate_out_at: full gate out - actual_gate_out_to_inland_depot_at / predicted_... - actual_delivered_at / predicted_delivered_at: at consignee - actual_empty_returned_at / predicted_empty_returned_at Current situation (latest confirmed milestone; all null if nothing has happened yet): - current_status: human-readable status, e.g. "Gate out full" - current_status_code: status code, e.g. "GT" - current_status_at: when it occurred, in that place's local time - current_status_timezone: IANA zone of the place it occurred - transshipments: intermediate port calls, each with port_name, port_code, timezone and arrival/departure times in that port's local time. Empty when the routing is direct. Do not present a ``predicted_*`` date as a fact - say "expected" or "estimated" for predicted and etd/eta fields.

search_containers