> ## 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 a Trip from Connect

> Book a real reservation to a GNet partner from the Connect dashboard with gBook — the path the Integration Robot rehearses

Most GNet trips are sent from an operator's own reservation system. When you want to send one by hand — to test a partner's new integration, to book with a partner your system is not connected to, or to see exactly what a partner receives — use **gBook** in the Connect dashboard.

gBook sends a **real** reservation. There is no sandbox on GNet: the trip is delivered to your partner's system the moment you click Book, and it stays live until it is completed or cancelled. Treat every test trip as one you will cancel.

<Note>
  If you are building a Farm In integration and just ran the [Integration Robot](https://dashboard.grdd.net/dashboard/integration-robot), this page is what your partners do instead of the robot. Same reservation, same statuses, same cancel — from a real partner account rather than from `gnettest`.
</Note>

## Who can see gBook

gBook appears in the **GNet** section of the dashboard menu for:

* Vendor Partner accounts (reservation platforms)
* Operators integrating directly against the GNet API
* Internal sandbox accounts

Any other operator can have it enabled on request — email [support@grdd.net](mailto:support@grdd.net) with the GRiDD ID. A platform testing its own integration usually asks for it on one of its customers' accounts, with that customer's permission, so the test trip travels the exact route a real order would.

## Before the first trip

Two things have to be true between the sender and the receiver, and both are checked before anything reaches the receiver's system.

<Steps>
  <Step title="The two accounts are partners">
    Open **My Partners** on the sender's dashboard. If the receiver is not listed under accepted partners, search the directory and send a request; the receiver accepts it from **My Partners → Incoming** on their dashboard.
  </Step>

  <Step title="The receiver has set the sender's account number">
    On the **receiver's** dashboard, open **My Partners**, select the sender, and fill in **Account Number** (the "pink field"). This is the sender's customer ID in the receiver's reservation system — it tells the receiving system who the trip is for. Bookings fail without it, with an error naming the missing account number. See [Account number: who the trip is for](/platform-api/receiving-reservations#account-number-who-the-trip-is-for).

    If the sender should also be able to ask the receiver for quotes, tick **Give Quotation Access** on the same screen.
  </Step>
</Steps>

## Sending the trip

<Steps>
  <Step title="Open gBook">
    Sign in at [dashboard.grdd.net](https://dashboard.grdd.net) and choose **gBook** under GNet in the menu. The page has the booking form on one side and your trips in progress on the other.
  </Step>

  <Step title="Trip">
    Select the **Partner** who will run the trip, the **Vehicle type**, the **Pickup date and time**, and the passenger count. Choose a pickup at least a couple of hours out — receiving systems refuse pickups inside their lead time, and a test trip should never sit in the past while you are watching it. For an hourly trip, set the duration.
  </Step>

  <Step title="Route">
    Enter the pickup and drop-off with the address picker rather than typing free text. A picked address arrives at the receiver both as one full line and split into street, city, state, zip and country, which is what receiving systems match on. For an airport, switch the location type to **Airport** and add the airline code and flight number; tick **Meet & Greet** if wanted. Add stops if the trip has any.
  </Step>

  <Step title="Passenger">
    Add the passenger's name and phone. You can pick a saved contact from your client list, and gBook will offer to save a new passenger to it before booking.
  </Step>

  <Step title="Show JSON (optional)">
    Click **Show JSON** to see the exact reservation GNet will deliver to the partner's system, without sending it. The payload is produced by the same code that sends it, so what you see is what they get. This is the fastest way for an integrating platform to confirm a field mapping before a real trip goes out.
  </Step>

  <Step title="Book">
    Click **Book**. The reservation is delivered to the partner immediately. A confirmation appears, the form clears, and the trip shows in your list with the **Sender Trip #** (yours) and, once the partner's system answers, the **Receiver Trip #** (theirs). If delivery fails, the error and any notes the partner's system returned are shown above the form.
  </Step>
</Steps>

## What the receiver gets, and what comes back

The receiver's system gets a reservation with `action: "NEW"`, the sender's account number, and the trip details, and answers with `success: true` and its own reservation number. From then on the receiver drives the trip and each status it pushes — `CONFIRMED`, `ASSIGNED`, `EN_ROUTE`, `ON_LOCATION`, `PASSENGER_ON_BOARD`, `COMPLETE`, `CLOSE` with final charges — appears on the sender's dashboard under **Reservations** and on the trip in gBook.

For the receiving side of this exchange, see [Receiving Reservations](/platform-api/receiving-reservations) and [Update Status by Reservation #](/platform-api/provider-updates/update-by-resno).

## Changing or cancelling the trip

From the trip list in gBook:

* **Edit** reloads the trip into the form. Change the pickup time, location, or passenger details and book again; the receiver gets the same reservation with `action: "UPDATE"` and your transaction ID.
* **Cancel Trip** sends `action: "CANCEL"`. The receiver's system must answer explicitly — `success: true` once cancelled in their dispatch, or `success: false` with a reason — and gBook shows you which. A refused cancel means the trip is still live on their side and needs a phone call. Cancelling close to pickup may incur the partner's late-cancellation charges, and gBook warns you before it sends.

These two are the part of an integration the [Integration Robot](/gnet-platform/certification#rehearse-it-yourself-first) covers least, and the part [certification](/gnet-platform/certification) weights most. Run both against any new partner integration before relying on it.

## Quotes are not orders

**Get Quotations**, also in the GNet menu, sends a `QUOTE` request, not a booking. The partner's system prices it (or does not) and nothing is dispatched. It only lists partners who have given you quotation access, and only works with partners whose systems answer quote requests. To send an order, use gBook.

<Card title="Contact Support" icon="headphones" href="mailto:support@grdd.net">
  To enable gBook on an account, or if a booking fails and the error is not clear.
</Card>