Skip to main content

Overview

The GNet platform is an integration platform that connects ground transportation companies, dispatch/reservation systems, and other custom integrations. Members of GNet can send (farm-out) and/or receive (farm-in) reservations. In this process, the sending party (also known as the requester) and the receiving party (the provider) are key players in ensuring smooth reservation transactions. GNet Platform Diagram Notes:
  • The requester and provider should establish a partnership in GNet Connect before conducting business with each other to ensure proper integration and service delivery.
  • For all API calls, you need to get the token using your API Gateway user.
  • Visit our YouTube playlist for detailed integration tutorials and walkthroughs.
  • For API reference: GNet Platform API.
  • For legacy Apiary reference: GNet API on Apiary

Interactive Setup Wizard

Prefer a guided experience? Try our interactive step-by-step wizard to see exactly how to connect to the GNet platform quickly and easily.

Authentication

  • Platform API requests (e.g., sendTrip, providerUpdateStatusByResNo) require a token header obtained from getToken2.
  • Your inbound Farm In endpoint should be protected (e.g., Basic Authentication using your issued API key/secret) and must accept JSON.

Sign Up to GNet

If you haven’t already, please complete the Sign Up page.
  1. Visit and sign up: https://connect.grdd.net/sign-up
  2. The GNet team will review and approve your account
  3. API credentials will be provided upon approval

Farm In (Receiving Reservations)

Please ask your technical team to create a webservice REST Endpoint (i.e. https://api.example.com/api/gnet-farmin) to accept POST requests with the following specifications:

Request Format

  • Method: POST
  • Headers:
    • content-type: application/json
    • Authorization: basic authentication (api_key/api_secret)
  • Body: JSON reservation payload (see sample)

Success Response

Error Response

Reservation Status Updates

Send reservation updates such as confirmations and status changes (including CONFIRMED, ASSIGNED, EN_ROUTE, ON_LOCATION) to this endpoint: Endpoint: https://api.grdd.net/Platform.svc/providerUpdateStatusByResNo/{GRIDDID}/{RESNO}/{VERSION} Headers:
  • token: <from getToken2>
  • Content-Type: application/json
For example, to accept a booking request:
For detailed documentation, see: Provider Update Status API and ( see other ASSIGNED payload example)
  • To see a list of all supported status codes, see Status Codes
  • To see a list of all supported vehicle types, see Vehicle Types

GPS Location Updates

Update current location of drivers using this API: Endpoint: POST https://location.grdd.net/api/GGPS.svc/saveGPScache Headers:
  • token: <from getToken2>
  • Content-Type: application/json

Sample Payload

Example curl:

Quote Requests

If the payload contains reservationType that is set to “QUOTE”:
  • Return the same payload structure as the Farm In success response
  • Include totalAmount in the response
  • You don’t need to create a reservation record in your database for quotes

Farm Out (Sending Reservations)

Step 1: Get Token

Step 2: Send Reservation

Example curl:

Step 3: Register Callback Webhook

Register a callback webhook to receive reservation updates from providers. Your endpoint should:
  • Accept POST requests
  • Return 200 status code
  • Process reservation updates
  • A sample payload will be sent to your webhook URL

Step 4: Send Booking Updates or Cancel Requests

Updates

Include transactionId in payload and set affiliateReservation.action to “UPDATE”

Cancel Request

For detailed documentation, see: Cancel Trip API

Testing

GBOOK Testing Utility

To test incoming trips, log in to the GBOOK utility:

Testing Steps:

  1. Log in to GBOOK
  2. Go to BOOK menu
  3. Select <griddid> from the affiliate dropdown box
  4. Fill in trip details and click BOOK
  5. You will receive the trip in your system
Note: Click “SHOW JSON” to see the exact payload structure you need to submit to GNet.

POSTMAN Collection

Download the complete collection: GNET.postman_collection.json

Setup:

  1. Import the collection
  2. Set environment variables:
    • token
    • requesterId
    • providerId
  3. Use the “Get Token” request first to obtain authentication token

Health Check

We use the Farm In Adapter GET endpoint for health checks. Expected Response:
  • Status code: 200
  • Body:
Example (assuming your Farm In endpoint is https://api.example.com/api/gnet-farmin):

Need Help?

Contact Support

Our support team is here to help you with integration questions and troubleshooting.

API Documentation

Complete API reference and detailed endpoint documentation.