---
title: Ocean
slug: fourkites-api-reference/_jbD-ocean
description: Learn how to create ocean loads in FourKites, a powerful tracking platform, using the Create Load API or the Booking API. This document provides sample fields and definitions for load creation, including shipment and stop details, asset information, and c
icon: {"faIcon":"fa-solid fa-ship"}
createdAt: 2023-08-03T17:54:08.000Z
---

:::hint{type="info"}
*Before you begin*: If your organization has limited data points about your ocean shipments, please check out the **Booking API **section which details a simple interface whereby one or more pieces of information from the booking can be provided to FourKites so that the load can be built directly from integrations with shipping lines or partner data platform
:::

## Ocean Load Structure

Ocean loads typically are created using one or several references from the booking (Container, MBOL, Booking Number, etc.) along with information about the port of loading and port of discharge. Optionally, drayage legs can be tracked.

![](https://api.archbee.com/api/optimize/2iLZ8zq0u-v-CPzk98WTR/KH_YaYFSGfeP9lTR0ULE2_151239588-fd658220-c8d0-4f35-a057-2b76ed32d7b9.png)

## Methods of Creating Ocean Loads

### Create Load API

Using the Create Load API to populate the full details of the load, including references, ports, and any additional stops which might be tracked is the first method of creating ocean loads. The implications of this method is that the organization creating the load in FourKites must have all of those data points on hand.

### Booking API

While it is sometimes the case that all details about the load are planned by the customer organization, there are situations where a freight forwarder or other entity might be managing the freight, meaning that the underlying customer might not have full details about ports, appointments, and other information.

Use the **Booking API** enables FourKites customers to bypass the need to have all information about the load. Specifically, limited information about the booking, such as Booking Number, Container Number, or Master Bill of Lading can be sent to FourKites so that the load details can be fetched directly from integrations with shipping lines or partner data platforms.

***

# Create Ocean Loads - Full Data

The following section details samples and recommended fields to create quality ocean or intermodal shipments for tracking. This section assumes that your organization has the full details about the ocean load and can supply information such as ports, ETD, ETA, and other information. If you do not have the full load details, please review the **Booking API** at the end of this section.

The fields shown in these samples follow recommendations, but the full list of available fields can be found in the fields list below.

FourKites supports different variations of ocean shipments, depending upon the level of tracking your organization is interested in capturing. Additional considerations should be made based upon the breadth of data managed directly within your organization.

- **Port-to-Port: **this is a purely ocean leg of the shipment and follows the container from the port of loading to the port of discharge
- **Port-to-Door: **in this scenario, the load would track the ocean leg from port of loading to port of discharge, and would also include the drayage leg or inland delivery to the final destination
- **Door-to-Port: **similar to the previous example, this would include an inland pickup stop en route to the port of loading. Next, the load would track the container across the ocean towards the port of discharge
- **Door-to-Door: **a full end-to-end sequence which tracks the load from the inland origin, port of loading, port of discharge, and final inland delivery. This is the most complex form of ocean tracking as it connects multiple legs of the journey using different modes