> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grdd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Sending Reservations

> Guidelines for building trip payloads sent over GNet

One standard format is needed for trip payloads to be sent over GNet to any target dispatch system. Follow the recommended guidelines below and you will have a glitch-free integration.

## 1. affiliateReservation section

This is the header section of the payload. It contains the GNet member ID of the sender, the receiver, and their reservation numbers. The `affiliateReservation.action` field serves as the command field that tells GNet what the payload is for. Valid values are `NEW`, `UPDATE`, and `CANCEL`.

The following fields are **required** when submitting a payload to GNet:

* `affiliateReservation.action`
* `affiliateReservation.requesterId`
* `affiliateReservation.providerId`
* `affiliateReservation.requesterResNo`

<Note>
  If submitting an `UPDATE` or `CANCEL`, then `affiliateReservation.providerResNo` is also required.
</Note>

## 2. Addresses

### Regular Addresses

Regular addresses are passed in two different formats in every address section:

* `locationType = "ADDRESS"`
* Full one-line address with street address, city, state, and zip included (no apartment numbers, no notes).
* The same address broken down into Street address, City, State, Zip, and Country.

### Airport Addresses

Airport addresses require IATA codes for airports and airlines. Use of IATA codes is **required**, otherwise airport trips cannot be understood.

* `locationType = "AIRPORT"`
* 3-character IATA code for the airport, placed in the `address` field.
* 2-character IATA code for the airline, placed in the `airlineCode` field.
* The actual flight number in the `flightNumber` field. Do not use `TBD` or similar — leave it empty if unknown.
* If the airport is an FBO, set the `FBO` field to `"True"` on that leg. Airline code `00` is another indication that the pickup or drop-off is an FBO.

## 3. Passengers

There must be at least one passenger in the passenger list. The passenger array is only limited by the target system's limits and can handle as many passengers as needed.

* Passenger **First Name** and **Last Name** are required.
* Phone numbers are recommended. If none is supplied and the target system requires one, GNet will use the sender's main office number as an alternate number.

## 4. Notes

There are different note sections in each payload:

* Each address section has a `specialInstructions` field — the notes for that address.
* Each trip payload has a `specialInstructions` field at the root level that holds the main trip notes.
* The `notes` array at the root level holds **Driver Notes** and **Affiliate Notes**.

## 5. Pickup Time format

Pickup, Drop-off, and Stop date/times are **local to the pickup location** and contain no timezone setting. The format for these fields is `YYYY-MM-DDTHH:mm:ss`.

```text theme={null}
2023-08-08T19:00:00
```

<Card title="Submit a reservation" icon="paper-plane" href="/platform-api/reservations/send-trip">
  Ready to send? See the sendTrip endpoint for the full request and response.
</Card>