Skip to main content
If an existing API does not already exist for GNet integration, you can consume GNet’s object model for receiving trips. GNet requires one web service on the receive side to accept NEW, UPDATE, and CANCEL requests — all in a single endpoint. To provide status updates for incoming trips, you call providerUpdateStatusByResNo on GNet. This endpoint should be called whenever there is a change in Status, Driver Info, Vehicle Info, Charge line items, or Total.
The GNet team will work with your technical team to determine how to communicate with your web service, capture confirmation numbers, and capture error messages in case a trip has to be rejected.

​
Interpreting the payload

The web service receiving trip payloads from GNet must look at the affiliateReservation section to determine whether the payload is requesting a NEW trip, or whether it is an UPDATE or CANCEL for an existing trip. affiliateReservation.action tells your web service what needs to be done:

​
Key fields

​
Providing status updates

Once you have received and accepted a trip, push status changes back to GNet by calling providerUpdateStatusByResNo or providerUpdateStatusByTransactionId. Send an update whenever any of the following change:
  • Status Code (see Status Codes)
  • Driver / Chauffeur info
  • Vehicle info
  • Charge line items (fees)
  • Total amount

Webhook Callbacks

GNet relays these updates back to the original sender via real-time webhook callbacks.