> ## 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.

# Search Overview

> The four GNet search endpoints, the service that hosts each one, how each authenticates, and when to use it.

## Search overview

GNet has two kinds of search: search for **operators (companies)** and search for **fleet vehicles**. Each kind exists on two different services. The four endpoints are separate. They have different parameters and different responses. Do not use one in place of another.

<Warning>
  Check the host before you call. **Core** (`core.grdd.net`) and the **Connect API service** are two different services with different paths, parameters, and error formats.
</Warning>

| Endpoint | Service and host | Finds | Auth | Page |
| - | - | - | - | - |
| `GET /api/company/search` | Core: `https://core.grdd.net` | Member companies | `Authorization: Bearer <token>` | [Search Members](/connect-api/search) |
| `GET /api/search/fleet` | Core: `https://core.grdd.net` | Fleet vehicles near airports or GPS points | `Authorization: Bearer <token>` | [Fleet Search](/connect-api/fleet-search) |
| `GET /api/search` | Connect API service: `$CONNECT_API_BASE_URL` | Active operator profiles | `Authorization: Bearer <token>`. `gateway` tokens are refused. | [Operator Search (Connect API)](/connect-api/search/connect-search) |
| `GET /api/fleets/search` | Connect API service: `$CONNECT_API_BASE_URL` | Fleet vehicles near one GPS point | `Authorization: Bearer <token>` | [Fleet Search (Connect API)](/connect-api/search/fleets) |

### Hosts and tokens

* Core hosts: `https://core.grdd.net` (production) and `https://core.grdd.dev` (development).
* The Connect API base URL is not published in these docs. Ask GRiDD support ([support@grdd.net](mailto:support@grdd.net)) for the Connect API base URL for your environment. The examples use `$CONNECT_API_BASE_URL`.
* Both services use a token that core issues. See the [Get Token API](/connect-api/get-token). The Connect API service verifies the token with core on each request.

### When to use each endpoint

* **Find a member company by name, city, country, airport, email, or map position, on core:** use [Search Members](/connect-api/search). It also supports a postal code search.
* **Find fleet vehicles near airports, on core:** use core [Fleet Search](/connect-api/fleet-search). It is the only fleet search that accepts airport codes.
* **Find operator profiles with plan-based result limits, badge filters, language choice, or service filters, on the Connect API service:** use [Operator Search (Connect API)](/connect-api/search/connect-search).
* **Find fleet vehicles near a GPS point and filter by verification or audit badge, on the Connect API service:** use [Fleet Search (Connect API)](/connect-api/search/fleets).

### Response and error formats

| Service | Success body | Error body |
| - | - | - |
| Core | `{"success": true, ...}` (company search uses `result`, fleet search uses `data`) | `{"success": false, "message": "..."}` |
| Connect API service, operator search | `{"items": [...], "totalFound": n, "nextCursor": null}` | Problem body with `code`, `message`, `correlationId`, `retryable` |
| Connect API service, fleet search | `{"success": true, "data": {...}}` | Problem body with `code`, `message`, `correlationId`, `retryable` |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.