Skip to main content

Operator Search (Connect API)

GET /api/search finds active GNet operator (company) profiles. You can search by name, place, map position, vehicle type, service, and audit badge. Each result is a fixed, public summary of one operator.
This endpoint runs on the Connect API service, not on core. It is a different endpoint from Search Members (GET /api/company/search on core). The two take different parameters and return different fields. Do not swap them. See the Search overview.

Base URL

The Connect API base URL is not published in these docs. Ask GRiDD support (support@grdd.net) for the Connect API base URL for your environment. The examples use a shell variable:

Endpoint

GET $CONNECT_API_BASE_URL/api/search

Authentication

Send a token that core issued. See the Get Token API.
The Connect API service verifies the token with core. Tokens with the gateway role are service credentials. This endpoint does not accept them. It returns 401 for a gateway token.

Query parameters

All parameters are optional. The service rejects any parameter that is not in this table with 400. You can repeat only vehicleType, service, and badge. Any other parameter that occurs twice gives 400. An empty value for a number parameter (for example latitude=) is invalid.

Plan limits

The service limits what each caller can receive. These limits come from the account’s plan. The service returns at most the smaller of limit and the plan limit. The badge filter works only for premium and enterprise plans. For other plans, the service removes badge and still runs the search. It does not return an error. The service has no paging. It returns one ranked window of up to 300 candidates. nextCursor is always null.

Example request


Success response

200 - OK
The response has no success field. The response headers include Cache-Control: no-store and X-Correlation-Id.

Response fields

Each item in items: The service does not return contact details, credentials, trial data, or internal scores.

Error responses

Errors use the application/problem+json content type:
reason and fieldErrors appear only when they apply. Use correlationId when you contact support. The service can also return 500 with internal_error for an unexpected failure.