> ## 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.

# Overview

> Integration reference for the GNet Platform API (Platform.svc)

## GNet Platform

GNet is an **Open Distribution Network** for ground transportation providers to send and receive reservations electronically. GNet acts as a messenger service that transmits reservations into target reservation systems and keeps these reservations synchronized until trip completion.

GNet is a B2B platform interfacing mainly with software companies that service Ground Transportation and Corporate Travel Service providers. Every transportation company is associated with a unique **GRiDD ID**. This ID identifies the providing company and ensures proper routing to the target back-office reservation system.

GNet Platform API services are **RESTful**.

## Actors

| Actor         | Description                                                             |
| ------------- | ----------------------------------------------------------------------- |
| **Requester** | An entity sending a reservation request to be fulfilled.                |
| **Provider**  | An operator who will fulfill the reservation.                           |
| **GNet**      | Platform to exchange reservations and provide real-time tracking.       |
| **Driver**    | Chauffeur.                                                              |
| **Vendor**    | Software vendors — Fasttrak Cloud, Livery Coach, Transdev, Hudson, etc. |
| **Passenger** | Primary passenger or traveler.                                          |
| **Account**   | Client account or requester account number.                             |

## Prerequisites

### Requester

* A requester must be connected to the GRiDD Platform™ and be assigned a GRiDD ID for reservations to be exchanged.
* A requester might be a transportation provider sending a reservation from their reservation system to an affiliate provider who uses a different reservation system.
* A requester may also be a Travel Management software and can use any choice of technology to integrate with the GRiDD API.

### Provider

* A provider must be connected to the GNet Platform™ and be assigned a GRiDD ID for reservations to be exchanged.
* A provider may use reservation systems that the GRiDD platform is already integrated into.

## Environments

| Environment    | Base URL                            |
| -------------- | ----------------------------------- |
| **Production** | `https://api.grdd.net/Platform.svc` |

Online API help is available at `https://api.grdd.net/Platform.svc/help`.

<Note>
  All endpoints require a `token` header obtained from [`getToken2`](/platform-api/authentication/get-token), except where noted.
</Note>

## How It Works

<CardGroup cols={2}>
  <Card title="Sending Reservations" icon="paper-plane" href="/platform-api/sending-reservations">
    Build a trip payload and submit it to GNet with `sendTrip`. Follow the recommended guidelines for a glitch-free integration.
  </Card>

  <Card title="Receiving Reservations" icon="inbox" href="/platform-api/receiving-reservations">
    Stand up a single web service to accept NEW, UPDATE, and CANCEL requests, and push status updates back to GNet.
  </Card>

  <Card title="Authentication" icon="key" href="/platform-api/authentication/get-token">
    Get a security token and pass it as a header on every call.
  </Card>

  <Card title="Object Model" icon="table-list" href="/platform-api/reference/object-model">
    The complete field-by-field reference for the reservation payload.
  </Card>
</CardGroup>

## HTTP Status Codes

| Code  | Description  |
| ----- | ------------ |
| `200` | Success      |
| `400` | Bad Request  |
| `401` | Unauthorized |