Search
Run query-driven retrieval through the Core API.
Documentation Index
Fetch the complete documentation index at: https://docs.neuronsearchlab.com/llms.txt
Use this file to discover all available pages before exploring further.
Description
Returns ranked catalog items for a free-text query. Search uses the Core API data plane athttps://api.neuronsearchlab.com/v1/search; it is not a Platform API or console search endpoint.
The search request embeds query, retrieves candidates, applies context filters and pipeline configuration, and returns the same recommendation item shape as GET /v1/recommendations.
Request
| Field | Type | Required | Description |
|---|---|---|---|
query | string | yes | Free-text query to embed and retrieve against. |
user_id | string | no | End-user identifier for telemetry, personalization context, and attribution. |
context_id | string | no | Numeric console context ID. Legacy ctx_ aliases such as ctx_101 are accepted. |
context_key | string | no | Context lookup key alias when your integration uses keys instead of numeric IDs. |
limit | string | no | Number of results to return. Defaults to 20, maximum 100. |
filter | string or string[] | no | Metadata filter shorthand. Repeat to combine filters. |
scope | string | no | JSON-encoded structured request scope, currently honoring filters. |
query_retrieval_enabled | string | no | Per-request override for query retrieval. Prefer configuring this in the active pipeline. |
fusion_method | string | no | rrf or weighted for semantic/keyword fusion. |
semantic_weight | string | no | Semantic retrieval weight when fusion_method is weighted. |
keyword_weight | string | no | Keyword retrieval weight when query retrieval is enabled. |
keyword_fields | string | no | Comma-separated metadata fields for keyword matching. |
Response
recommendations with the same result array as data. Responses may include embedding_info, request-level explanation, and per-item explanation fields.
Use the returned request_id in downstream events to attribute engagement to the search result set. The official JavaScript and PHP SDKs capture it automatically after search().
Errors
| Status | Scenario |
|---|---|
400 | Validation failed or malformed filters |
401 | Missing/invalid access token or tenant resolution failed |
403 | Token does not include neuronsearchlab-api/read |
422 | Search query embedding is unavailable for the team |
500 | Unexpected search, database, or model-serving failure |
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
Optional stable request ID for retries and downstream event attribution. The same ID is returned in the response body and X-Request-Id response header.
Optional session identifier stored with served search telemetry.
Optional anonymous identifier stored with served search telemetry when user_id is absent.
Optional SDK name stored with served search telemetry.
Optional SDK version stored with served search telemetry.
Optional client platform stored with served search telemetry.
Body
Free-text query to embed and retrieve against.
1"waterproof trail shoes"
End-user identifier for telemetry, personalization context, and attribution.
"usr_abc123"
Numeric console context ID. Legacy ctx_ aliases such as ctx_101 are also accepted.
"101"
Context lookup key alias when your integration uses keys instead of numeric IDs.
Number of results to return. Defaults to 20 and is capped at 100.
1 <= x <= 100"10"
Metadata filter shorthand. Examples: category:footwear, type!=comment, OR:brand:Acme.
["category:footwear"]
JSON-encoded request scope. Today only filters is honored, using objects with column, operator, value, and optional logic.
"{\"filters\":[{\"column\":\"brand\",\"operator\":\"=\",\"value\":\"Acme\"}]}"
Per-request override for query retrieval. Prefer configuring this in the active pipeline.
Semantic/keyword fusion strategy.
rrf, weighted Semantic retrieval weight when fusion_method is weighted.
0 <= x <= 1Keyword retrieval weight when query retrieval is enabled.
0 <= x <= 1Comma-separated fields or array of fields for keyword matching.
"name,description,category"
Optional stable request ID for retries and attribution. Prefer the X-Request-Id header.
Response
Search results fetched.
list "/v1/search"
- Option 1
- Option 2
- Option 1
- Option 2
1 <= x <= 100x >= 0x >= 0single, auto "waterproof trail shoes"
"Search results fetched"
Present in auto mode.

