API access
Tenant-scoped Search API

Add intent-aware search without rebuilding your product around it.

Querix gives product teams one authenticated API for exact filters, broad catalog browsing, and natural-language discovery. Start with the integration contract; use the platform and data guides when your team needs deeper context.

Read the API guide Request API access
First search requestHTTPS · JSON

Request

POST /api/v1/<tenant>/search

X-API-Key: <server-side-key>

{
  "query": "bike in Chennai under 1000",
  "page_size": 20
}

Response

200 OK
{
  "items": [{ "id": "p_1042", "title": "City Bike" }],
  "interpreted_query": {
    "category": "bicycles",
    "location": "Chennai",
    "max_price": 1000
  },
  "pagination": { "has_more": true, "next_cursor": "..." }
}
public fieldssafe filtersnext cursor

Canonical API surface

A small contract for the complete search lifecycle.

Every company receives a tenant slug and server-side key. Your backend integrates the endpoints below; Querix owns retrieval, ranking, cursors, and search operations.

Checking APILive serving-path probe
POST
/{tenant}/search

Search

Start an intent-aware search or continue an existing cursor session.

GET
/{tenant}/auth/verify

Verify access

Confirm that an issued API key belongs to the requested tenant endpoint.

GET
/{tenant}/health

Tenant health

Inspect the search dependencies behind one authenticated company experience.

GET
/{tenant}/usage

Usage

Retrieve tenant-scoped monthly request accounting for reporting.

Server-side credentials

Every issued key is bound to a tenant endpoint and stays behind your backend boundary.

Isolated by contract

Keys, public fields, limits, cursors, cache state, and search storage remain tenant-scoped.

Health you can act on

Use public readiness for traffic checks and authenticated health for tenant dependencies.

Tenant onboarding

From provisioned tenant to measured launch.

The integration is small, but a reliable launch also covers catalog quality, relevance acceptance, and operational ownership.

  1. 01

    Provision the tenant contract

    Agree the tenant slug, public response fields, source mapping, limits, and any compatibility adapter required by an established client.

  2. 02

    Prepare and publish the catalog

    Run tenant normalization and validation, then atomically promote a complete retrieval dataset.

  3. 03

    Integrate through your backend

    Keep the tenant key server-side and expose only the search behavior your web or mobile client needs.

  4. 04

    Accept relevance with real demand

    Exercise exact, semantic, multilingual, zero-result, cursor, fallback, and concurrency cases from representative customer queries.

  5. 05

    Launch with measurable operations

    Gate traffic on readiness, monitor authenticated tenant health, and review separate company and internal daily analytics.

Documentation paths

Start with the contract. Go deeper when you need to.

Start here · API integration

Ship your first tenant-scoped search flow.

Authentication, backend proxy patterns, request and response contracts, cursor pagination, errors, and launch checks.

Read guide

Search platform

Know what the API handles for you.

Structured browse, intent-aware discovery, result freshness, tenant boundaries, and routing behavior.

Read guide

Architecture summary

Review the request flow and trust boundaries.

A concise view of routing, data freshness, tenant isolation, and predictable failure behavior.

Read guide

Data lifecycle

See how catalog data becomes search-ready.

Read-only source refresh, tenant normalization, retrieval content, quality gates, incremental updates, and atomic publishing.

Read guide

Service reliability

Plan for health, freshness, and failure.

Readiness, tenant health, index refreshes, observable fallback behavior, and production assurance.

Read guide

Your tenant key belongs behind your application.

Browser and mobile clients should call your backend proxy. Querix examples use placeholders intentionally; issued keys, admin diagnostics, and private data never belong in public source or client-visible configuration.

Need help with your integration?

Talk to us about your catalog and search contract.

Contact engineering