However even though the data sent in the POST /transports is valid the OceanIO system might not be able to find information about the container. One reason could be that the carrier has not updated their system with information that they are transporting the given container in the near future. Or it could be that the entered vessel_operator_carrier_code is wrong so the requested carrier will not transport the given container any time soon.
In case a valid POST /transports have been made against the OceanIO system but it is not possible to find information about the container then the OceanIO will create a message (an alert) that is available by polling the GET /exceptions endpoint. The exceptions/alerts can also be sent to your system by configuring a webhook. See Using the push option.
Message in the exceptions stream:
{"type": "gatehouse.com/errors/no_equipment_found""title": "Equipment could not be found""error_code": 1027,"status": 404,"detail": "We could not find equipment with reference 'MMMU1234567'.""reference": "MMMU1234567","reference_type": "Equipment","carrier_scac": "SCAC"}
For explanation of the error message see Error handling.
7 days retention on event data
The events in the data stream will be available in the stream for 7 days. This means that if you haven’t called GET /events for more than 7 days then the oldest events will be removed by the system. The same is the case for the push of events. If the customers API that is receiving events are down in more than 7 days, then the oldest events will be removed from the system
