sendTrip Payload Update - GNet Documentation

Release Date: May 2026 · Product: GNet Platform · Endpoint: POST /Platform.svc/sendTrip · View API Docs

New Fields

Two new optional fields have been added to the sendTrip request payload.

1. `namesignURL` string · optional

A URL pointing to a pre-generated namesign asset for passenger pickup. Supported file types: HTML, PDF, or an image. Best practice for URL structure (not required, but recommended):

# Extension-based
https://example.com/booking/123456789/namesign.pdf
https://example.com/booking/123456789/namesign.png
https://example.com/booking/123456789/namesign.html

# Parameter-based
https://example.com/booking/123456789/namesign?format=PDF
https://example.com/booking/123456789/namesign?format=PNG

Usage guidance:

Farming out (sending trips to a partner operator)

Include namesignURL in the payload so the receiving operator can display the namesign to their driver.

Receiving farm-in jobs

If the inbound payload contains a namesignURL, your system should render it. On mobile devices, display it full-screen for easy passenger identification at pickup.

2. `tripAttributes` array · optional

An array of structured attribute objects describing special requirements or services for the trip. The code field is required on each item; all other fields are optional. Schema:

Field	Type	Required	Description
`code`	string	✅ Yes	Identifies the attribute type (see codes below)
`value`	string	No	Specific value for the attribute
`quantity`	integer	No	Numeric quantity where applicable
`notes`	string	No	Free-text notes for the driver

Supported codes:

Code	Description	Common `value` options
`CAR_SEAT`	Child car seat requirement	`INFANT`, `TODDLER`, `BOOSTER`
`SECURITY_SERVICE`	Security personnel or escort	—
`DISABILITY_SERVICE`	Accessibility accommodation	`WHEELCHAIR_ACCESSIBLE`
`CHILD_SAFETY`	General child safety flag	—

JSON example:

"tripAttributes": [
  { "code": "CAR_SEAT", "value": "INFANT", "quantity": 1, "notes": "rear-facing" },
  { "code": "CAR_SEAT", "value": "BOOSTER", "quantity": 1 },
  { "code": "SECURITY_SERVICE" },
  { "code": "DISABILITY_SERVICE", "value": "WHEELCHAIR_ACCESSIBLE" },
  { "code": "CHILD_SAFETY" }
]

Backward Compatibility

Both fields are optional. Existing integrations require no changes. If your platform does not send these fields, trip processing is unaffected.

Questions?

Contact the GNet Platform team at support@grdd.net.

​New Fields

​1. namesignURL string · optional

​2. tripAttributes array · optional

​Backward Compatibility

​Questions?

New Fields

1. `namesignURL` string · optional

2. `tripAttributes` array · optional

Backward Compatibility

Questions?