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.
Release Date: May 2026 · Product: GNet Platform · Endpoint:
POST /Platform.svc/sendTrip
· View API DocsNew Fields
Two new optional fields have been added to thesendTrip 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):
Farming out (sending trips to a partner operator)
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
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 |
| 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 | — |
Backward Compatibility
Both fields are optional. Existing integrations require no changes. If your platform does not send these fields, trip processing is unaffected.