Force update
Ask the shipping line about this shipment now and wait for its answer, up to 25 seconds. The body is the same record as container detail, shortened in the example here, plus a refresh block that says what happened. When the line answered in time, refresh.refreshed is true. When it did not, data is the last answer we hold, refresh.from_cache is true and refresh.reason says why; after a timeout the ask keeps running and a later read serves its answer.
Counted: REST: 1 call per keyed request, whatever the route answers; a quota refusal is not counted. See what counts as a successful request.
Path parameters
The container UUID, or a container, bill of lading or booking number your account tracks.
Response schema
964 fields
Generated from the OpenAPI spec. Nested exactly as the JSON is. Open a branch to read its fields; hover a name for the full dot-path.
Whether the request succeeded.
The response contract this build answers, as a date.
data
The payload.
Stable identifier for the record.
Your organisation.
The container number, or null when the record was tracked by a bill of lading or booking that has not yet resolved to a box.
The bill of lading, or null when the record was not tracked by one.
The booking reference, or null when the record was not tracked by one.
Carrier SCAC.
Carrier name.
ISO 6346 size and type code as the carrier filed it, for example 45G1.
Size in TEU: 1 for a 20ft box, 2 for a 40ft.
Plain-language equipment type, for example Reefer or Dry.
Current normalised status of the shipment.
Origin port UN/LOCODE, or null when the carrier named no origin we could resolve.
Destination port UN/LOCODE, or null when unresolved.
Origin port name, falling back to its UN/LOCODE.
Destination port name, falling back to its UN/LOCODE.
Arrival time (ISO 8601) of the vessel (the ARRI event) at the port in destination_unlocode: planned until it arrives, actual after (see eta_is_estimated).
True when the ETA is still a forecast, false when it is the actual arrival, null when there is no ETA at all.
How often this lane arrives on time, as a percentage.
When the box was discharged, which is when free time starts counting.
Free days the terms allow at this port.
The last day free of charge, computed from the discharge and the free days.
True when the free-time clock on this box is a concern.
Demurrage charged so far on this box, US dollars.
Your own labels on this box.
Your own free-text note on this box.
When you started tracking this box (ISO 8601).
When we last asked the carrier (ISO 8601).
Which polling cadence this box sits in (pre_departure, transit, arrival, dwell).
When tracking stopped, or null while the box is still active.
The container number, bill of lading or booking this record tracks.
What the identifier is.
IMO of the hull carrying the box now.
Carrier voyage number for the current leg.
Daily demurrage rate in force at the destination, US dollars.
The last day before demurrage accrues, or null when no terms are on file.
What caused the most recent carrier check: a schedule, your recheck call, or a webhook.
Latitude from a physical IoT tracker on the box, when you feed us one.
Longitude from that device.
When the device last reported.
True when the device raised an alert, for example a door opening or a temperature excursion.
Why customs is holding the box, when the carrier names a reason.
When the hold started.
Equipment size, for example 40HC.
Equipment family as the carrier names it.
The type half of the ISO 6346 code (G1 for a general-purpose box, R1 for a reefer).
When we gave up resolving this reference.
A route problem we detected, for example a destination change or a missed connection.
Departure the carrier planned or actually filed for the load port.
Name of that hull.
Cargo (gate) cutoff at the load port.
VGM filing cutoff.
Shipping-instruction cutoff.
Customs-release cutoff at the load port.
cutoff_enrichment
What the line returned beside the events: the boxes of a document, the route it states, and line-specific extras. Free-form: the keys inside depend on the shipping line, so the ones listed here are examples, not a fixed set.
Every container number on the bill of lading or booking, as listed by the carrier.
How many containers the document names, including any the carrier has not numbered yet.
One entry per container on the document that has its own timeline. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
containers[]
Container number.
Normalised size and type, for example 40HC.
ISO 6346 size and type code, for example 45G1.
The carrier's size and type string before normalisation.
True when this timeline was fetched for this container specifically and is not a copy of the shipment timeline.
sourced when the carrier returned movements for this container, no_data when it answered and published none.
This container's own events, in the same shape as an event raw_payload. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
events[]
The event instant in UTC (ISO 8601).
IANA time zone of the event port, null when it could not be resolved.
UN/LOCODE of the event place, null when none is known.
True when the event happened, false when it is planned or estimated.
Place name as the carrier wrote it.
Normalised event code, for example LOAD, DISC, GTIN, GTOT, ARRI, DEPA, STUF, STRP, AVPU, CUSR, CUSI, CUSS; an unmapped carrier code passes through as written.
IMO number of the vessel on this move, null when unknown or not a plausible IMO.
The carrier's wording for the event.
Which kind of source produced the event: carrier when the line answered directly; any other value means the event reached us another way.
Name of the vessel on this move.
Family the code belongs to: EQUIPMENT, TRANSPORT or SHIPMENT.
Carrier voyage number for this move.
What the connector emitted before normalisation: utc for a true instant, port_local for a port wall clock.
The wall clock at the event port as a zoneless ISO string, for example 2026-07-21T11:07:00.
How the instant was established: carrier_offset, tz_resolved, date_only, local_unplaced or legacy_unknown.
Mode of transport for the leg: VESSEL, RAIL, TRUCK or BARGE, null when not stated.
How precise the carrier was: datetime, or date when it gave a day with no time.
Local time minus UTC in minutes at that instant, null when the port zone is unknown or the event is date only.
The exact rung the source was resolved on, kept verbatim so a coarse bucket never hides the detail.
The classifier the carrier itself gave, ACT, EST or PLN, present only when the line tells an estimate from a plan.
What the line itself said about the move: actual, plan, or unstated when it gave a date with no such word.
The UTC offsets in minutes that the zone abbreviation printed by the carrier can mean.
Where the code came from: carrier for the line's own code, derived when filled from the place name, corrected when we replaced the line's code.
The line's own code for the place when we replaced it with a corrected one.
Two-letter country code the carrier stated for the place.
Which port of the journey the carrier says this move happened at: origin, transshipment or destination.
The port a facility-only row belongs to, taken from the line's own ordering.
The carrier's own event code before normalisation, kept verbatim for forensics.
SCAC of the sister line that stated this move when it was merged in from a carrier group answer.
Terminal, depot or other facility name for the move.
UN/LOCODE the source gives for the facility.
BIC facility code, when the source publishes one.
SMDG terminal code, when the source publishes one.
Latitude of the facility in decimal degrees.
Longitude of the facility in decimal degrees.
Two-letter country code of the facility.
Set to computed when the mode is our conclusion and not the line's own word.
The carrier's own status wording kept verbatim as a remark beside a normalised code.
True when the carrier itself published the DCSA code and it was passed through unchanged.
Whether the box was EMPTY or LADEN on this move, null or absent when not established.
Set to line_sequence when the laden or empty state was read from the order of the line's own list and not from its wording.
True when the carrier hands the box straight to its next shipment without an empty move.
Trade direction the carrier states for the move: EXP for the export side, IMP for the import side.
True for a port call of the ship where the box stays aboard and is not handled.
On a shipment event, the booking or transport document the event is about.
On a shipment event, BKG for a booking or TRD for a transport document.
Set to observed when the line stated the fact without a date and the time is when we first saw it.
Zero-based position of this step in the line's own ordered journey list.
Set to implied_by_later_actual when the step counts as actual only because a later actual of the line proves it happened.
Container number the event belongs to, set on a per-container row derived from a document.
The legs of the route held for this shipment; the fields of a leg vary by where the legs came from. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
stated_route
The route the line states in its own answer, one statement per place it names, in its order.
statements[]
Role of the place on the route: POR, POL, TSP, POD or FND.
place
The place as the line names it.
The place as the line wrote it.
The line's own UN/LOCODE for the place, null when it gives none.
arrival
The arrival the line states for this place, null when it states none.
The port calendar day or wall clock as the line gives it, zoneless, for example 2026-10-15 or 2026-10-15T09:30.
The line's own word: true for estimated, false for actual, null when it says neither.
departure
The departure the line states for this place, null when it states none.
The port calendar day or wall clock as the line gives it, zoneless, for example 2026-10-15 or 2026-10-15T09:30.
The line's own word: true for estimated, false for actual, null when it says neither.
Our UN/LOCODE for each place of stated_route that the line left uncoded, keyed by the place text as the line wrote it.
Which surface of the carrier's answer this enrichment was read from.
schedule_derived_pod
Present when the discharge port was filled from the published sailing schedule because the line named none.
IMO number of the vessel the sailing was matched on.
Voyage number the sailing was matched on.
UN/LOCODE of the load port the sailing was matched on.
UN/LOCODE of the discharge port taken from the sailing.
Arrival the schedule publishes for that port, which is not promoted to an ETA.
Label of the schedule record the sailing came from.
Why a reference could not be resolved: invalid_number, not_found or bl_booking_unresolved.
When the record itself last changed in our database, which includes bookkeeping writes.
Why tracking stopped: your delete call, or an automatic close-out once the box finished its cycle.
Internal bookkeeping: when the "container identified" digest was sent for this box.
Internal bookkeeping: when a lessor or intermediary lookup last enriched this record.
Groups every box created by one bulk import, so their digest fires once per batch.
Carrier seal on the box.
The scope of the move the carrier is performing, for example port to port or door to door.
Verified gross mass, kilograms.
Gross weight of the loaded box, kilograms.
Pieces inside the box.
Unit the package count is in, for example CTN or PLT.
Cargo volume, cubic metres.
A special handling requirement filed on the shipment, for example a reefer set point.
Commercial details the line states for the shipment (for example service type, operator, release states). Free-form: the keys inside depend on the shipping line, so the ones listed here are examples, not a fixed set.
The surface the box was added from.
Where the answer on this call came from: direct_carrier or warm_db.
route_data
The route in the shape our map consumers read: the legs, the current pin and the AIS block.
The legs of the drawn route.
route[]
from
Where the leg starts.
Latitude.
Longitude.
Human-readable name.
State, province or region of the port, when the gazetteer holds one.
UN/LOCODE of the place.
Country name.
IANA time zone of the place.
ISO 3166-1 alpha-2 country code.
to
Where the leg ends.
Latitude.
Longitude.
Human-readable name.
State, province or region of the port, when the gazetteer holds one.
UN/LOCODE of the place.
Country name.
IANA time zone of the place.
ISO 3166-1 alpha-2 country code.
The drawn geometry of the leg as lat and lng pairs.
Event code, for example DEPA or LOAD.
vessel
Vessel currently carrying the container, or null when we hold neither a name nor an IMO.
IMO number of the ship, as a number.
Name of the ship.
MMSI of the ship.
Radio call sign of the ship.
Flag state of the ship.
The mode carrying the leg, for example VESSEL or TRUCK, when the carrier names it.
The clean port to port corridor of the shipment, given when path also carries the sailed track of the ship.
Set to ais_track when the leg was drawn from the positions the ship itself reported.
Which runs of path the ship itself reported, as inclusive [start, end] index pairs into path.
What the line is: routed along a sea lane, a direct straight segment, or absent.
Why the leg has no line.
True when the path crosses the 180 degree meridian, so a flat map must split or unwrap it.
Where to draw the box right now, as a lat and lng pair.
How the pin was placed: ais_vessel_position from a real fix, route_reckoning when computed along the route, or a port when the box is sitting at one.
ais
The vessel and port dates as an AIS-shaped block, kept in the layout integrators migrating from the older API already parse.
data
The AIS-shaped payload.
vessel
The hull these dates belong to.
IMO number of the vessel.
Flag state of the vessel, as a two-letter code.
Vessel MMSI.
Human-readable name.
Vessel radio call sign.
last_event
The most recent vessel move behind these dates.
When it happened, as a port wall-clock string without an offset, which is the layout this block has always used.
Carrier voyage number, when published.
The carrier own phrasing for the event, falling back to our word for the code.
When this AIS block was last rebuilt.
arrival_port
The arrival call these dates describe.
The short port code the compatible API prints next to the UN/LOCODE.
UN/LOCODE of the place.
The date of the call, as a port wall-clock string with no offset, which is the layout this block has always used.
Which kind of date the neighbouring value is: ETA, ETD, ATA or ATD.
ISO 3166-1 alpha-2 country code.
departure_port
The departure call these dates describe.
The short port code the compatible API prints next to the UN/LOCODE.
UN/LOCODE of the place.
The date of the call, as a port wall-clock string with no offset, which is the layout this block has always used.
Which kind of date the neighbouring value is: ETA, ETD, ATA or ATD.
ISO 3166-1 alpha-2 country code.
discharge_port
The discharge call these dates describe.
The short port code, as above.
UN/LOCODE of the place.
The date of the sea discharge, in the same wall-clock layout.
Which kind of date the neighbouring value is: ETA, ETD, ATA or ATD.
ISO 3166-1 alpha-2 country code.
Human-readable name.
last_vessel_position
The most recent fix for the hull, with the time it was taken.
Latitude.
Longitude.
When the fix was taken.
Whether the AIS block carries data, and why not when it does not.
source
Who produced the route and the AIS in this block.
Machine name of the producer.
Display name of the producer.
How the drawn line was produced, for example trackingmcp_computed.
Which vessel-position source fed the AIS block.
One sentence of provenance in plain language.
True when the pin was computed rather than observed.
The observation the estimate was anchored to.
Which generation of our route-drawing produced this geometry.
Identifier of the chart validation the route was drawn against; null when none is loaded.
When we calculated the estimated marker position; null when the marker is not an estimate.
Distance from the marker to the drawn route, in whole kilometres.
True when the marker sits close enough to the drawn route to agree with it.
Which position the agreement check rested on; only vessel_fix is an independent test of the route. One of: vessel_fix, port_anchor, estimate.
Distance from the latest AIS fix of the ship to the drawn route, in whole kilometres; null when there is no fix.
When this route block was last built.
Registered owner of the box, resolved from its BIC prefix.
Leasing company, when the box is leased rather than carrier-owned.
Who holds the box on lease.
An unconfirmed carrier candidate derived from lessor data.
The box status as the lessor reports it, for example on-hire or off-hire.
When we last asked the lessor.
Redelivery booking for the empty.
When the empty is due back.
Where the empty is due back.
The depot the empty is due back at.
Lease contract the box sits on.
Lease type, for example long-term or one-way.
Who built the box.
When the box went on hire.
Where it went on hire.
The depot it went on hire at.
Where a request to connect this carrier stands, when the line needs one.
When you asked to be told the connector went live.
When we told you it went live.
field_provenance
Per-field account of WHY a declared field is empty, keyed by field name.
{field}
Why the field stands where it does: resolved, contract_required, not_published, not_applicable or awaiting_carrier.
What would change the state: supply_terms, wait, or do_not_expect when nothing will.
Where the answer on this call came from: direct_carrier or warm_db.
On a card, whether the slot partners agree with each other.
The reasoning behind the state, in one sentence, so a support answer does not need our source.
field_provenance_summary
Counts of the declared cutoff and demurrage fields by state, so you can tell "we do not have it" from "your contract terms would unlock it".
Declared fields we hold a value for.
Declared fields that stay empty until you supply your own free-time terms.
Declared fields this carrier does not publish.
Declared fields that do not apply to this shipment.
Declared fields we expect but have not received yet.
True when supplying free-time terms would fill at least one empty field.
carrier_response_raw
The same object as cutoff_enrichment, served under a second name. Free-form: the keys inside depend on the shipping line, so the ones listed here are examples, not a fixed set.
Every container number on the bill of lading or booking, as listed by the carrier.
How many containers the document names, including any the carrier has not numbered yet.
One entry per container on the document that has its own timeline. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
containers[]
Container number.
Normalised size and type, for example 40HC.
ISO 6346 size and type code, for example 45G1.
The carrier's size and type string before normalisation.
True when this timeline was fetched for this container specifically and is not a copy of the shipment timeline.
sourced when the carrier returned movements for this container, no_data when it answered and published none.
This container's own events, in the same shape as an event raw_payload. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
events[]
The event instant in UTC (ISO 8601).
IANA time zone of the event port, null when it could not be resolved.
UN/LOCODE of the event place, null when none is known.
True when the event happened, false when it is planned or estimated.
Place name as the carrier wrote it.
Normalised event code, for example LOAD, DISC, GTIN, GTOT, ARRI, DEPA, STUF, STRP, AVPU, CUSR, CUSI, CUSS; an unmapped carrier code passes through as written.
IMO number of the vessel on this move, null when unknown or not a plausible IMO.
The carrier's wording for the event.
Which kind of source produced the event: carrier when the line answered directly; any other value means the event reached us another way.
Name of the vessel on this move.
Family the code belongs to: EQUIPMENT, TRANSPORT or SHIPMENT.
Carrier voyage number for this move.
What the connector emitted before normalisation: utc for a true instant, port_local for a port wall clock.
The wall clock at the event port as a zoneless ISO string, for example 2026-07-21T11:07:00.
How the instant was established: carrier_offset, tz_resolved, date_only, local_unplaced or legacy_unknown.
Mode of transport for the leg: VESSEL, RAIL, TRUCK or BARGE, null when not stated.
How precise the carrier was: datetime, or date when it gave a day with no time.
Local time minus UTC in minutes at that instant, null when the port zone is unknown or the event is date only.
The exact rung the source was resolved on, kept verbatim so a coarse bucket never hides the detail.
The classifier the carrier itself gave, ACT, EST or PLN, present only when the line tells an estimate from a plan.
What the line itself said about the move: actual, plan, or unstated when it gave a date with no such word.
The UTC offsets in minutes that the zone abbreviation printed by the carrier can mean.
Where the code came from: carrier for the line's own code, derived when filled from the place name, corrected when we replaced the line's code.
The line's own code for the place when we replaced it with a corrected one.
Two-letter country code the carrier stated for the place.
Which port of the journey the carrier says this move happened at: origin, transshipment or destination.
The port a facility-only row belongs to, taken from the line's own ordering.
The carrier's own event code before normalisation, kept verbatim for forensics.
SCAC of the sister line that stated this move when it was merged in from a carrier group answer.
Terminal, depot or other facility name for the move.
UN/LOCODE the source gives for the facility.
BIC facility code, when the source publishes one.
SMDG terminal code, when the source publishes one.
Latitude of the facility in decimal degrees.
Longitude of the facility in decimal degrees.
Two-letter country code of the facility.
Set to computed when the mode is our conclusion and not the line's own word.
The carrier's own status wording kept verbatim as a remark beside a normalised code.
True when the carrier itself published the DCSA code and it was passed through unchanged.
Whether the box was EMPTY or LADEN on this move, null or absent when not established.
Set to line_sequence when the laden or empty state was read from the order of the line's own list and not from its wording.
True when the carrier hands the box straight to its next shipment without an empty move.
Trade direction the carrier states for the move: EXP for the export side, IMP for the import side.
True for a port call of the ship where the box stays aboard and is not handled.
On a shipment event, the booking or transport document the event is about.
On a shipment event, BKG for a booking or TRD for a transport document.
Set to observed when the line stated the fact without a date and the time is when we first saw it.
Zero-based position of this step in the line's own ordered journey list.
Set to implied_by_later_actual when the step counts as actual only because a later actual of the line proves it happened.
Container number the event belongs to, set on a per-container row derived from a document.
The legs of the route held for this shipment; the fields of a leg vary by where the legs came from. Each item is free-form: its keys depend on the shipping line, so the ones listed here are examples, not a fixed set.
stated_route
The route the line states in its own answer, one statement per place it names, in its order.
statements[]
Role of the place on the route: POR, POL, TSP, POD or FND.
place
The place as the line names it.
The place as the line wrote it.
The line's own UN/LOCODE for the place, null when it gives none.
arrival
The arrival the line states for this place, null when it states none.
The port calendar day or wall clock as the line gives it, zoneless, for example 2026-10-15 or 2026-10-15T09:30.
The line's own word: true for estimated, false for actual, null when it says neither.
departure
The departure the line states for this place, null when it states none.
The port calendar day or wall clock as the line gives it, zoneless, for example 2026-10-15 or 2026-10-15T09:30.
The line's own word: true for estimated, false for actual, null when it says neither.
Our UN/LOCODE for each place of stated_route that the line left uncoded, keyed by the place text as the line wrote it.
Which surface of the carrier's answer this enrichment was read from.
schedule_derived_pod
Present when the discharge port was filled from the published sailing schedule because the line named none.
IMO number of the vessel the sailing was matched on.
Voyage number the sailing was matched on.
UN/LOCODE of the load port the sailing was matched on.
UN/LOCODE of the discharge port taken from the sailing.
Arrival the schedule publishes for that port, which is not promoted to an ETA.
Label of the schedule record the sailing came from.
UN/LOCODE of the place where the line hands the box over.
Name of the place of delivery as the line states it.
UN/LOCODE of the port of loading: where the box boarded its first ship on this trip, read from its first vessel load (the line's own "at Port of Loading" load when it files one).
Name of the port of loading as the line states it on that load.
origin_coord
Coordinate of the origin port.
Latitude.
Longitude.
True when the coordinate is a place centroid rather than a terminal position.
What the approximate point was derived from.
destination_coord
Coordinate of the destination port.
Latitude.
Longitude.
True when the coordinate is a place centroid rather than a terminal position.
What the approximate point was derived from.
True on a sample reference.
The boxes a bill of lading or booking resolves to, each with its own timeline and its own status (with status_source: tracked when your organisation also tracks the box on its own line, line when read from the events the line filed for that box on this document, document when the document holds no per-box events and none of its events names another box, so the box shows the document's own status, which can be a stage read from the vessel's AIS, such as at_berth or at_anchor; both null when none has reported one).
child_containers[]
Container number of the box, or TBA for a group of boxes the line has not numbered yet.
ISO equipment type code of the box, for example 45G1.
The line's own size and type label for the box.
The box's own status, which can differ from the status of the document. One of: pre_departure, in_transit, at_transshipment, arriving, at_anchor, at_berth, discharged, customs_hold, available, delivered, returned_empty.
Where the box status came from: its own tracked row, the line's events for that box, or the document status.
The box's own timeline; an empty array when no per-box timeline is known yet.
events[]
Milestone code of the move, for example GTIN, LOAD, DEPA, ARRI, DISC or GTOT.
Readable name of the move, the same wording the dashboard shows.
Family the move belongs to.
Conveyance the line stated for the move.
True when the move has happened, false when it is planned or estimated.
True when a planned move is served as done because a later actual move proves it happened.
When the move happened or is planned, as a UTC instant when the port time zone is known.
The same moment on the port wall clock, without an offset.
IANA time zone of the port, for example Asia/Shanghai.
Minutes to add to UTC to get the port wall clock.
How the timestamp was obtained, so a client knows whether it is a true instant. One of: carrier_offset, tz_resolved, date_only, local_unplaced, legacy_unknown.
UN/LOCODE of the place of the move.
Where the served UN/LOCODE came from. One of: carrier, matched_in_country, matched_port_name, corrected, not_determined, recorded.
Place name as the line wrote it.
Terminal, depot or other facility name as the line wrote it.
Name of the ship for this move.
IMO number of the ship for this move, as a string.
Voyage number the line stated for this move.
The line's own wording for the move.
The line's own status remark for the move.
Whether the box was empty or laden at this move.
Who stated the fill state: the line, or nobody.
What a gate-out did: moved the box on, or handed it to the consignee. One of: transfer, consignee_delivery, not_reported.
The leg_sequence of the entry in legs[] this move belongs to, or null when no served ocean leg claims it.
ais_eta
Our own arrival projection from the live vessel position, beside the ETA of the line.
Projected arrival at the port.
Always ais_position.
Distance left to the port, in nautical miles.
Speed used for the projection, in knots.
Signed hours against the ETA of the line: positive means the projection is later.
How far to trust the projection.
Milestone timeline, oldest to newest.
events[]
Stable identifier for the record.
Your organisation.
The container number this row is about.
The id this event carries on the DCSA /v2 surface, so the same physical event can be matched across both surfaces.
DCSA event category: SHIPMENT, TRANSPORT or EQUIPMENT.
DCSA classifier: ACT, EST or PLN.
When the event happened or is forecast to (ISO 8601).
When we recorded the event, not when it happened.
DCSA transport code on a vessel move: ARRI for arrival, DEPA for departure.
Carrier code for why a move slipped.
The carrier own free-text remark about a change to this event.
DCSA equipment code on a box move, for example GTOT for a gate-out or LOAD for a load.
EMPTY or LADEN on an equipment event.
The container the event happened to.
ISO 6346 equipment code as filed on this event.
DCSA shipment code on a documentation move.
The document the shipment event refers to, on the lines that publish one.
What that document is, for example a bill of lading.
The carrier stated reason for the event, on the lines that publish one.
transport_call
The location, vessel and voyage of the port call.
location
UN/LOCODE for the event, or null when the carrier gave no place.
Port name as the carrier wrote it, unmapped.
UN/LOCODE.
Conveyance the line stated for the move. One of: VESSEL, RAIL, TRUCK, BARGE.
facility
The terminal, depot or other facility of the move.
Who supplied the facility codes.
Facility name as the line wrote it.
UN/LOCODE of the facility.
SMDG terminal code of the facility.
BIC facility code.
The single facility code to use: the SMDG code when known, else the BIC code.
Which code list facilityCode comes from.
Latitude of the facility.
Longitude of the facility.
Two letter country code of the facility.
vessel
The ship of the move.
Name of the ship.
IMO number of the ship as a string; null when the value the line sent cannot be an IMO number.
Name of the ship, duplicated under the DCSA key.
Voyage number the line stated for the move.
Voyage number of the move, on rows rebuilt from a per-box timeline.
Extra carrier references filed against the event.
Seal numbers filed against the event.
How sure we are of the normalised code: REPORTED when the carrier gave a code we map directly, INFERRED when we derived it from its wording, UNKNOWN when neither was possible.
The code the source used, before normalisation.
The source own event object, kept verbatim.
When the record was created (ISO 8601).
The carrier own id for the event, when it publishes one.
Same instant as event_date_time, under the name the earlier API used.
Machine-readable event code, for example LOAD, DISC, GTIN, GTOT, ARRI, DEPA.
raw_payload
The connector event exactly as it was stored, so a value we did not map is never lost. Free-form: the keys inside depend on the shipping line, so the ones listed here are examples, not a fixed set.
The event instant in UTC (ISO 8601).
IANA time zone of the event port, null when it could not be resolved.
UN/LOCODE of the event place, null when none is known.
True when the event happened, false when it is planned or estimated.
Place name as the carrier wrote it.
Normalised event code, for example LOAD, DISC, GTIN, GTOT, ARRI, DEPA, STUF, STRP, AVPU, CUSR, CUSI, CUSS; an unmapped carrier code passes through as written.
IMO number of the vessel on this move, null when unknown or not a plausible IMO.
The carrier's wording for the event.
Which kind of source produced the event: carrier when the line answered directly; any other value means the event reached us another way.
Name of the vessel on this move.
Family the code belongs to: EQUIPMENT, TRANSPORT or SHIPMENT.
Carrier voyage number for this move.
What the connector emitted before normalisation: utc for a true instant, port_local for a port wall clock.
The wall clock at the event port as a zoneless ISO string, for example 2026-07-21T11:07:00.
How the instant was established: carrier_offset, tz_resolved, date_only, local_unplaced or legacy_unknown.
Mode of transport for the leg: VESSEL, RAIL, TRUCK or BARGE, null when not stated.
How precise the carrier was: datetime, or date when it gave a day with no time.
Local time minus UTC in minutes at that instant, null when the port zone is unknown or the event is date only.
The exact rung the source was resolved on, kept verbatim so a coarse bucket never hides the detail.
The classifier the carrier itself gave, ACT, EST or PLN, present only when the line tells an estimate from a plan.
What the line itself said about the move: actual, plan, or unstated when it gave a date with no such word.
The UTC offsets in minutes that the zone abbreviation printed by the carrier can mean.
Where the code came from: carrier for the line's own code, derived when filled from the place name, corrected when we replaced the line's code.
The line's own code for the place when we replaced it with a corrected one.
Two-letter country code the carrier stated for the place.
Which port of the journey the carrier says this move happened at: origin, transshipment or destination.
The port a facility-only row belongs to, taken from the line's own ordering.
The carrier's own event code before normalisation, kept verbatim for forensics.
SCAC of the sister line that stated this move when it was merged in from a carrier group answer.
Terminal, depot or other facility name for the move.
UN/LOCODE the source gives for the facility.
BIC facility code, when the source publishes one.
SMDG terminal code, when the source publishes one.
Latitude of the facility in decimal degrees.
Longitude of the facility in decimal degrees.
Two-letter country code of the facility.
Set to computed when the mode is our conclusion and not the line's own word.
The carrier's own status wording kept verbatim as a remark beside a normalised code.
True when the carrier itself published the DCSA code and it was passed through unchanged.
Whether the box was EMPTY or LADEN on this move, null or absent when not established.
Set to line_sequence when the laden or empty state was read from the order of the line's own list and not from its wording.
True when the carrier hands the box straight to its next shipment without an empty move.
Trade direction the carrier states for the move: EXP for the export side, IMP for the import side.
True for a port call of the ship where the box stays aboard and is not handled.
On a shipment event, the booking or transport document the event is about.
On a shipment event, BKG for a booking or TRD for a transport document.
Set to observed when the line stated the fact without a date and the time is when we first saw it.
Zero-based position of this step in the line's own ordered journey list.
Set to implied_by_later_actual when the step counts as actual only because a later actual of the line proves it happened.
Container number the event belongs to, set on a per-container row derived from a document.
The port wall-clock for the same moment, naive and with no offset, exactly as a terminal prints it.
Minutes to add to the UTC instant to reach the local wall-clock.
IANA zone of the port, which survives a DST change in a way a bare offset cannot.
True when the carrier published a calendar date with no time of day.
The calendar date, YYYY-MM-DD, when date_only is true.
Internal marker for how this row timestamp was established.
The step in plain language, for example Gated out.
Who stated the fill state of an equipment event: carrier when the line reported EMPTY or LADEN, not_reported when it did not.
What a gate-out did, in the line's own words: transfer when the line says the box moved on (to another terminal, a rail ramp or a train), consignee_delivery when it says the consignee took the box, not_reported when it says neither.
The leg_sequence of the legs[] ocean leg whose voyage this event belongs to: the leg its own ship and voyage name, else the leg that loads or discharges at its port, else the voyage last discharged before it (so the rail haul, the delivery and the empty return after discharge belong to the last ocean leg).
True when the line named a terminal, hub or depot for this arrival.
journey_context
Marks a move that is part of a transshipment.
Always transshipment.
Which side of the transshipment the move is. One of: discharged_for_transshipment, loaded_on_onward_vessel.
Where the served UN/LOCODE of the event came from. One of: carrier, matched_in_country, matched_port_name, corrected, not_determined, recorded.
True when a planned move is served as done because a later actual move proves it happened.
True on a past plan the line left behind a later actual move, shown as the line gave it.
The shipment as a reader story: carrier events plus the moves we inferred between them, in order.
journey_timeline[]
Stable identifier for the record.
carrier_event when a carrier filed it, trackingmcp_inference when we derived the step from surrounding events.
DCSA classifier: ACT for actual, EST for estimated, PLN for planned.
When the step happened (UTC).
The step in plain language, for example Gated out.
Resolved port UN/LOCODE.
Resolved port name.
Terminal or depot inside the port, when the carrier names one.
The event ids this step was built from, so an inference can always be traced back.
On a card, whether the slot partners agree with each other.
The event in plain words.
The role the port plays on this route: origin, transshipment or destination.
The voyage milestone this step marks, when it marks one.
Count of shipments in an exception state: customs hold, rolled, delayed or at transshipment.
exceptions[]
What kind of exception this is. One of: inspection_started, scanner_flagged, carrier_hold, exam_selected, document_hold, declaration_rejected, inferred_silent_hold, eta_at_risk.
Whether the line reported it, we inferred it, or it is a forecast.
How serious it is.
When the hold started; always null for eta_at_risk.
Short label for a badge.
One or two sentences explaining the exception.
What to do about it now.
Whether it comes from a carrier event or from our own inference. One of: carrier_event, trackingmcp_inference.
How far back the timeline reaches on your plan, in days.
current_leg
The leg the box is on now.
Order of the leg on the journey, starting from the first leg.
Whether the leg is carried on water or over land.
UN/LOCODE where the leg starts.
UN/LOCODE where the leg ends.
IMO number of the ship sailing the leg, as a string.
Name of the ship sailing the leg.
Internal voyage identifier.
The carrier's voyage number for the leg, read from the box's own timeline.
Arrival at the end of the leg: estimated until it happens, then the actual time.
When the box actually came off at the end of the leg; null while the leg is still open.
True on a leg that was added from the line's stated route and has no ship, voyage or dates yet.
The voyage broken into legs.
legs[]
True only for an undated connection inferred from the carrier-declared destination and known preceding port, including owner-confirmed terminal-to-delivery on-carriage.
Order of the leg on the journey, starting from the first leg.
Whether the leg is carried on water or over land.
UN/LOCODE where the leg starts.
UN/LOCODE where the leg ends.
IMO number of the ship sailing the leg, as a string.
Name of the ship sailing the leg.
Internal voyage identifier.
The carrier's voyage number for the leg, read from the box's own timeline.
Arrival at the end of the leg: estimated until it happens, then the actual time.
When the box actually came off at the end of the leg; null while the leg is still open.
planned_vessel
The ship the box is waiting for: before its first actual load while its planned load at the port of loading is still ahead or at most 3 days past, or at a transshipment hub before the reload.
Name of the planned ship.
IMO number of the planned ship, as a string.
Voyage number of the planned sailing.
position
Latest AIS position of the planned ship; null when the fix is older than 48 hours, the plan has lapsed, or the ship has already left the load port.
Latitude of the ship.
Longitude of the ship.
When the ship was observed at this position.
heading_to
The port where the box is planned to load.
UN/LOCODE of the planned load port.
Name of the planned load port.
When the box is planned to load onto this ship.
Always planned.
eta_overdue
Set when the served ETA has passed, the line reports no arrival and has gone quiet.
The served ETA that has passed.
Whole days since that date.
When the line last put anything new on this box.
One sentence you can show as-is.
ais_pod_arrival
Our AIS observation of the carrying vessel arriving at the port of discharge, when the line has not filed the arrival yet.
When the vessel was first seen at the port on its final stay there.
UN/LOCODE of the port of discharge.
Name of the port.
IANA zone of the port, for printing observed_at on the port clock.
IMO number of the vessel.
Name of the vessel.
How far from the port the qualifying position lay.
Always ais: our observation of the vessel, never an event the line filed.
One sentence you can show as-is.
ais_pol_departure
AIS saw the vessel carrying the box leave its port of loading while the line has not reported a departure there: the box's last actual load at that port names the vessel, nothing has discharged it there since, and the vessel's call at that port spans the load.
When the ship left the port of loading, by our AIS port call record.
UN/LOCODE of the port of loading.
Name of the port of loading.
IANA time zone of the port of loading.
IMO number of the ship.
Name of the ship.
Always ais.
A sentence you can show as-is.
vessel_position
Live AIS position of the carrying vessel.
IMO number of the vessel.
Human-readable name.
Latitude.
Longitude.
Speed over ground, in knots.
Heading in degrees.
Navigational status as reported by AIS, for example "Under way using engine" or "Moored".
When we last wrote the position row.
When the hull was actually observed.
The destination ETA the vessel itself is broadcasting, which is the master own entry and often disagrees with the carrier.
Destination port UN/LOCODE, or null when unresolved.
Photograph of the hull.
When the vessel particulars were last refreshed.
The navigational status the vessel broadcasts, unchecked.
False when the broadcast status contradicts where the vessel actually is, for example Moored while far from any port.
Why the broadcast status was not trusted, for example outside_port_geofence.
Distance to the nearest port, nautical miles, which is the evidence behind the check.
When we checked the position for this request.
When this request started a live AIS refresh because the stored fix was older than 20 minutes; null when none was started.
How the pin was placed: ais_vessel_position from a real fix, route_reckoning when computed along the route, or a port when the box is sitting at one.
What the reckoning leaned on when the pin was computed rather than observed, for example a published schedule.
The observation the estimate was anchored to.
observed_position
The last position we actually observed, never a computed one.
Latitude.
Longitude.
When the fix was taken.
How exact the fix is: precise for a terrestrial fix, coarse for a satellite one.
Radius the fix is good to, kilometres.
estimated_position
A computed position, for when there is no fresh fix.
Latitude.
Longitude.
The moment the estimate describes.
The observation the estimate was reckoned from.
Which reckoning class produced the estimate.
How the position was produced, for example route_reckoning.
vessel_photo
Photograph of the current hull with its attribution.
Where we POST the events.
Where the answer on this call came from: direct_carrier or warm_db.
When we fetched the photograph.
The more recent of the carrier check and the AIS fix: when we last learned anything about this shipment.
Which of the two produced last_updated_at: carrier_poll or ais_vessel_position.
When the vessel was last actually observed by AIS, or null when we hold no fix.
Vessel names by IMO number, for every vessel named on the legs.
transshipment
The hub the box is dwelling at and its onward vessel.
UN/LOCODE of the hub, when the line gave one.
Place name of the hub as the line wrote it.
When the box was discharged at the hub, which starts the waiting clock.
Name of the ship that brought the box to the hub.
IMO number of the ship that brought the box to the hub.
Name of the ship the box is planned to load onto.
IMO number of the ship the box is planned to load onto.
Estimated arrival of the next ship at the hub, when the line publishes it.
Planned departure of the box from the hub on the next ship.
hubCoord
Map coordinate of the hub; null when the hub cannot be placed.
Latitude of the hub.
Longitude of the hub.
True when the point is a country level fallback and not the real port.
UN/LOCODE the approximate position was borrowed from.
schedule_overlay
The published vessel rotation we matched this box to, which is the plan against which actuals can be read.
Where the answer on this call came from: direct_carrier or warm_db.
How strongly the sailing matches the box, strongest first: vessel_voyage, vessel_lane, vessel_route, onward_vessel_lane, lane, carrier_lane.
Carrier SCAC.
Carrier service or loop name.
IMO number of the carrying vessel, or null when unknown.
Carrier voyage number.
The departure the carrier published (ISO 8601).
The arrival the carrier published (ISO 8601).
Port-to-port transit in days.
True when the box changes vessel on the way.
The voyage broken into legs.
legs[]
Position of the leg in the rotation, starting at 1.
UN/LOCODE the leg departs.
UN/LOCODE the leg arrives at.
Name of the departure port.
Name of the arrival port.
Name of the carrying vessel, or null when the carrier named none.
Carrier voyage number, when published.
Carrier service or loop name.
Estimated time of departure (ISO 8601).
Arrival time (ISO 8601).
eta_intel
Probability envelope and reliability context.
What the reliability figures were computed from, which tells you how much to lean on them.
True when the statistics are for THIS carrier on this lane, false when they are lane-level across all carriers and therefore coarser.
On-time percentage for the lane, which is the same number the ring shows.
Share of sailings that arrived on time.
Typical delay on the lane, hours.
Delay that 90 percent of arrivals stay inside, hours.
Number of observed sailings behind the figure.
How far back those observations reach, days.
Best case: the published ETA, arriving on time.
The date 90 percent of arrivals land by.
The typical outcome: the ETA plus the median delay.
Median transit time on the lane, hours.
Transit time 90 percent of sailings stay inside, hours.
eta_at_risk
Congestion warning.
Always true when the object is present.
UN/LOCODE of the next port the box calls at.
Readable sentences explaining the risk, one per signal.
Congestion level at the next port; null when the risk comes only from the ship.
Expected extra waiting time at the next port, in days.
How long this ship recently waited at anchor, in hours.
Which kinds of signal the warning is based on. One of: ais_wait, port_index, ais, ais_density, vessel_dwell.
observability
Which of the four lenses we can offer on this shipment, and how many are active.
lenses
actuals (carrier milestones), position (the vessel), plan (a schedule) and probability (a confidence figure).
True when we hold carrier milestones.
True when we hold a vessel.
On LoadingMCP, the computed load plan.
True when the ETA can carry a confidence figure.
How many of the four lenses are present.
Whether the sources tell the same story: aligned, diverging, partial, or insufficient when there are too few to compare.
The ETA each cross-checkable source implies, so a disagreement can be seen rather than averaged away.
eta_sources[]
Which source this ETA came from: carrier, published or ais.
Arrival time (ISO 8601).
Hours between the furthest-apart ETA sources.
A written read of the shipment state.
True while one is being generated, so a client can poll instead of showing an empty space.
carrier_document_reply
Latest retained, exact-reference OOCL document reply.
carrier_notice
Latest reference-specific reply from the named carrier.
One of: other_carrier, temporarily_unavailable, not_found, invalid_reference, SHIPMENT_CANCELLED, no_longer_available.
line_suggestion
Another line that answered this container directly, shown when the line you named has no record of it.
The ETA on the destination port's own clock, with no offset: YYYY-MM-DDTHH:MM:SS, or a bare YYYY-MM-DD when the line gave a date and no time.
The IANA time zone of the destination port (for example Europe/Amsterdam), to label eta_local.
Our own forecast of the arrival (ISO 8601), served beside eta (the line's date where it gave one).
The line's own published arrival, as parsed from its answer.
Stored source of our arrival forecast: carrier_eta shifted by the hull's measured slip at its next port.
Signed minutes of the slip behind predicted_eta.
ais_delay_propagation when a forecast was published, else why none was (for example no_carrier_eta, no_ais_eta, port_mismatch, delay_immaterial).
When the forecast fields above were last evaluated.
Why eta is null although the route is known.
The sailing the line published for the port of loading (its ETD or estimated on board date).
Shipped-on-board date stated on your bill of lading (from a document you uploaded).
Who named carrier_code: user (you), lessor (the box owner's records), detected (our resolver) or admin (our support team).
When a person last named carrier_code.
The carrier code you named, before any of our rules changed it.
A corrected form of identifier that a line answered for, offered as "did you mean".
When suggested_reference was found.
suggested_reference_evidence
What the line returned for the suggested reference.
The line that answered for the suggestion.
Vessel the line names for it.
Voyage the line names for it.
Port of loading the line names for it.
Port of discharge the line names for it.
How many containers the line lists on it.
How many events the line returned for it.
Time of the newest event the line returned for it.
How the suggestion differs from what you typed.
When the line confirmed the suggestion.
When the line itself last answered for this box with at least one event.
When the line says it last updated this record.
Start of your own trip for this box: the line's trip that was in progress when you added it.
End of your own trip, set once the line moved on to the box's next trip.
active once the line answered, pending while the first answer is still loading (query again rather than cache the nulls), not_found when the reference never resolved.
tracking_activity
Whether the box is still moving or has gone quiet.
Whole days since the newest actual event.
Whole days past the later of ETA and the last actual event.
One sentence you can show as-is.
The milestones we inferred (never filed by the line), also merged into journey_timeline.
derived_milestones[]
Stable identifier for the record.
carrier_event when a carrier filed it, trackingmcp_inference when we derived the step from surrounding events.
DCSA classifier: ACT for actual, EST for estimated, PLN for planned.
When the step happened (UTC).
The step in plain language, for example Gated out.
Resolved port UN/LOCODE.
Resolved port name.
Terminal or depot inside the port, when the carrier names one.
The event ids this step was built from, so an inference can always be traced back.
On a card, whether the slot partners agree with each other.
The event in plain words.
The role the port plays on this route: origin, transshipment or destination.
The voyage milestone this step marks, when it marks one.
display_position
The one pin to draw for the box: an AIS fix or, between fixes, a position reckoned along the route.
True when reckoned along the route, not observed.
Every hull this box was reported on, oldest first.
vessel_history[]
True when the box was moved off the vessel it was booked on.
rollover
The latest vessel change, when rollover_detected is true.
previous_vessel
new_vessel
The reference the shipment is tracked by.
What kind of reference identifier is.
previous_trip
The trip before yours for this box, when the line still reports it.
The line that answered, as its SCAC.
last_event
Every event of that trip, oldest first.
events[]
On a bill of lading or booking: true when legs covers only part of the route its boxes travel.
On a document with two or more boxes: true when its boxes are not all at the same stage.
On a document with two or more boxes: true when only some of them are discharged.
A note for leasing-company accounts when no line holds the box yet.
ais_status_suggestion
A hint that AIS shows the hull under way while the line still files pre-departure.
evidence
The AIS facts the suggestion rests on.
Navigation status the ship reported over AIS.
Distance of the ship from the load port, in whole kilometres.
When the ship was observed at that position.
True when the ship is within 100 km of the destination port.
Internal bookkeeping: the user who added the reference, when a person did.
Internal bookkeeping: the API key the reference was added with.
Internal bookkeeping: which meter counts this box.
Internal bookkeeping: how we decided what kind of reference this is.
line_event_order
Internal bookkeeping: the line's own step order, as we stored it.
Logical keys of the events in the order the line listed them.
When this order was recorded.
Internal bookkeeping: when we next ask about a box between trips.
Internal bookkeeping: when the reference was last added; null reads as added_at.
Internal bookkeeping: when the reference was added from the web app.
resume
Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
body
The reference to add again.
refresh
What a force update achieved.
True when the line answered in this request.
True when the detail is the answer we already held, not one from this request.
Null when fresh. One of: line_timeout, line_no_answer, refresh_failed.
When the line last answered about this shipment: this request when fresh, else the answer shown.
True while the ask is still running after the response (the timeout case).
error
Only on status 202, 401, 403, 404, 409, 429, 500, 503 and 504.
Machine readable error code.
Human readable explanation.
How serious the error is.
True.
The reference.
Seconds to wait.
Offending fields.
CONTAINER_QUOTA_EXCEEDED only.
Tokens this request needs.
Tokens the wallet holds.
Where to top up.
Plans on offer.
packages[]
Plan key.
Tokens per month.
Monthly price in USD.
CARRIER_NOT_IDENTIFIED only.
CARRIER_NOT_IDENTIFIED, timed out only.
The member cycle limit.
Tokens the member has used this cycle.
Tokens left for the member.
Seconds until the next refresh is allowed.
progress
One of: SEALINE_HASNT_PROVIDE_INFO, NO_EVENTS, WRONG_NUMBER, REFERENCE_REQUIRED, LINE_NOT_SUPPORTED, PENDING, UNRESOLVED.
previous_trip
The trip before yours for this box, when the line still reports it.
The line that answered, as its SCAC.
last_event
events[]
A note for leasing-company accounts when no line holds the box yet.
One of: in_progress, not_supported, connected, reference_required.
carrier_notice
Latest reference-specific reply from the named carrier. Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
One of: other_carrier, temporarily_unavailable, not_found, invalid_reference, SHIPMENT_CANCELLED, no_longer_available.
Present when the line named was not used. Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
Known line that cannot be asked. Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
upgrade
CONTAINER_QUOTA_EXCEEDED only. Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
Next plan.
Monthly price.
Annual price.
Why the line named was not used. Only on status 202, 401, 403, 404, 409, 500, 503 and 504.
Errors
A failure carries { "ok": false, "error": { "code", "message", "severity" } }. Branch on the code, and log the message.
Not a failure. The shipment has no tracking data yet. The body carries error.retry_after_seconds and the refresh block. Retry after the Retry-After header.
The key is missing, malformed or revoked.
The key is read-only. A force update needs a read_write key.
No such shipment on your account.
The shipment is archived, so the line is not asked again. data.archived_at says when tracking stopped. To track it again, add the reference with POST /containers.
This shipment was force updated with this key less than 5 minutes ago. Retry after the Retry-After header; error.retry_after carries the same seconds.
We could not read the record just now. Retry shortly.
curl -X POST 'https://api.navo24.com/v1/tracking/containers/8f1c2d4e-6a3b-4f52-9c70-11ab22cd33ef/refresh' \
-H "Authorization: Bearer tmcp_YOUR_API_KEY"const res = await fetch("https://api.navo24.com/v1/tracking/containers/8f1c2d4e-6a3b-4f52-9c70-11ab22cd33ef/refresh", {
method: "POST",
headers: {
"Authorization": "Bearer tmcp_YOUR_API_KEY"
}
});
const data = await res.json();import requests
res = requests.post(
"https://api.navo24.com/v1/tracking/containers/8f1c2d4e-6a3b-4f52-9c70-11ab22cd33ef/refresh",
headers={"Authorization": "Bearer tmcp_YOUR_API_KEY"},
)
data = res.json(){
"api_version": "2026-08-04",
"ok": true,
"data": {
"id": "8f1c2d4e-6a3b-4f52-9c70-11ab22cd33ef",
"container_number": "HLXU8765432",
"carrier_code": "ONEY",
"carrier_name": "ONE",
"status": "in_transit",
"eta": "2026-10-17T22:00:00+00:00",
"eta_is_estimated": true
},
"refresh": {
"status": "fresh",
"refreshed": true,
"from_cache": false,
"reason": null,
"requested_at": "2026-11-10T09:00:00.000Z",
"updated_at": "2026-11-10T09:00:01.000Z",
"refreshing_in_background": false
}
}