Skip to main content

Fleet Search API

The Fleet Search API lets you discover available vehicles from all GNet operators near a given location. Search by vehicle type (e.g., sedan, SUV) and specify a location using airport codes or GPS coordinates. Results include vehicle details, photos, capacity, and the operator’s GPS position.

Endpoint

GET https://core.grdd.net/api/search/fleet Authorization: Bearer <your_token>

Query Parameters

Location requirement: Provide at least one of airports or lat+lon. Both can be combined — operators near any of the given locations are included.

Example Requests

Search by airport code

Search by GPS coordinates

Multi-airport search with custom radius

Returns only fleet records where both “rolls” and “royce” appear across the name, description, model, or type fields. Combine with types to further narrow results.

Success Response

200 - OK

Returns a list of fleet vehicles matching the search criteria. The list is cross-operator — vehicles from all GNet operators serving the requested location(s) are included.

Response Fields

data.items[]

data.warnings[]

Warnings are non-fatal notices returned alongside results. Warning codes:
  • UNRESOLVABLE_AIRPORT — An airport code in the request could not be resolved to GPS coordinates. Valid codes in the same request are still searched.
  • MISSING_GPS — An operator has a service location record near the search point but no parseable GPS coordinates. That operator is excluded from results.

Error Responses

401 - Unauthorized

400 - Bad Request

Returned when no location is provided, or when lat and lon are not both present.

500 - Internal Server Error


Notes

Sort order

Results are sorted by two criteria applied in order:
  1. Distance (ascending) — operators nearest the search point(s) appear first. Distance is grouped into 5 km buckets, so an operator 3 km away and one 4.9 km away are treated as equally close.
  2. Completeness score (descending) — within the same distance bucket, operators with richer vehicle profiles (photo, description, capacity info, extras) rank higher. Scores range from 0 to 100; the score field is included in each result for reference.
This ensures that a 0.01 km distance difference does not bury a significantly better-described operator.
  • Results are cross-operator: vehicles from every active GNet operator serving the search area are included in a single response.
  • When multiple airport codes or a mix of airports and GPS coordinates are provided, operators near any of the given points are included (union).
  • An operator appearing in multiple location results is deduplicated — they appear once, with GPS from the location closest to the first matched search point.
  • The types filter is case-insensitive (Sedan, SEDAN, and sedan all match).
  • When types is omitted, all vehicle types from matching operators are returned.
  • radius_km defaults to 50 km when not specified.
  • limit defaults to 20 and is capped at 100. Use offset to page through results (offset=20 for page 2, offset=40 for page 3, etc.).
  • total in the response always reflects the full match count before pagination, so callers can compute total pages as ceil(total / limit).