Redpine Connect
API referenceSearch

Search a single collection by name

Shorthand for POST /api/v1/search/query with the collection named in the path instead of the body. Same pipeline, same response shape, one collection per call — use /query's `collections` form to search several at once.

POST
/api/v1/search/{collection}

Authorization

BearerAuth
AuthorizationBearer <token>

API key authentication. Pass your key in the Authorization header as Bearer sk_live_.... An X-API-Key: sk_live_... header is also accepted as an alternative. Keys are created in the Redpine Connect dashboard under Settings > API Keys.

In: header

Path Parameters

collection*string

Name of the collection to search.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Same knobs as SearchRequest minus collection/collections — the target collection is the path segment, so a collection key in the body is rejected.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v1/search/string" \  -H "Content-Type: application/json" \  -d '{    "query": "string"  }'
{  "filterWarnings": null,  "journalMetricExpansions": null,  "latencyMs": 0,  "queryId": "string",  "results": [    {      "collection": null,      "id": "string",      "metadata": null,      "text": "string"    }  ]}
Was this page helpful?