Skip to main content

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.

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

ActorDescription
RequesterAn entity sending a reservation request to be fulfilled.
ProviderAn operator who will fulfill the reservation.
GNetPlatform to exchange reservations and provide real-time tracking.
DriverChauffeur.
VendorSoftware vendors — Fasttrak Cloud, Livery Coach, Transdev, Hudson, etc.
PassengerPrimary passenger or traveler.
AccountClient 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

EnvironmentBase URL
Productionhttps://api.grdd.net/Platform.svc
Online API help is available at https://api.grdd.net/Platform.svc/help.
All endpoints require a token header obtained from getToken2, except where noted.

How It Works

Sending Reservations

Build a trip payload and submit it to GNet with sendTrip. Follow the recommended guidelines for a glitch-free integration.

Receiving Reservations

Stand up a single web service to accept NEW, UPDATE, and CANCEL requests, and push status updates back to GNet.

Authentication

Get a security token and pass it as a header on every call.

Object Model

The complete field-by-field reference for the reservation payload.

HTTP Status Codes

CodeDescription
200Success
400Bad Request
401Unauthorized