API overview

The Neuji Search API returns private, ad-free search results as JSON — the same web, image, news, video, and shopping results that power Neuji, with no advertising, tracking, or query logging.

Base URL

The API is region-aware. Use the base URL for your account's region:

Both regions serve the same endpoints and accept the same keys; the region affects only the default result weighting. The examples below use api.neuji.com; swap the host for your region.

Authentication

Every request must carry your API key as a bearer token:

Authorization: Bearer neuji_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Create a key in your Neuji account — see Authentication. The billable search endpoints require an active Neuji membership and a positive API credit balance.

A first request

curl "https://api.neuji.com/v1/search?q=hello+world" \
  -H "Authorization: Bearer $NEUJI_API_KEY"

using var http = new HttpClient();
http.DefaultRequestHeaders.Authorization =
    new("Bearer", Environment.GetEnvironmentVariable("NEUJI_API_KEY"));
var json = await http.GetStringAsync("https://api.neuji.com/v1/search?q=hello+world");
Console.WriteLine(json);

const res = await fetch("https://api.neuji.com/v1/search?q=hello+world", {
  headers: { Authorization: `Bearer ${process.env.NEUJI_API_KEY}` },
});
console.log(await res.json());

Responses

A successful response is JSON with HTTP 200. An error uses a uniform envelope:

{ "error": { "type": "invalid_request", "message": "Query parameter 'q' is required.", "request_id": "a1b2c3d4e5f6a7b8" } }

Every response carries an X-Request-Id header (echoed as request_id in errors); quote it when contacting support. Errors lists the full set of types and status codes, and Rate limits describes throttling.

Versioning

The current version is v1, reached under the /v1 path prefix. New fields may be added to responses without a version bump, so parse defensively and ignore unknown fields. A breaking change would ship under a new version prefix.

Endpoints at a glance