Search Query Parse API Specification & Integration Reference
Public API Page

POST Search Query Parse API

/api/v1/ai/search-query-parse

Convert messy, natural-language search queries into structured, normalized search instruction parameters for your own search engine or database.

Base Billing 1 Credit
Target Latency < 150ms (p50)
Client Timeout 5.0s (recommended)
SLA Guarantee 99.9% Uptime
JSON Contract Deterministic v1

Architecture Role & AI Definition

Search Query Parse API provides low-latency, deterministic REST execution for production engineering workflows. It processes structured payloads with strict schema validation, returns uniform JSON envelopes, and is secured via SHA-256 API key authentication with atomic credit pre-authorization locks.

Production Reliability Guidelines

1. Strict Timeout Windows

Configure a hard client timeout of 5 to 8 seconds. If network latency spikes, cancel connection to avoid holding open sockets in worker pools.

2. Exponential Backoff with Jitter

Upon receiving 429 Rate Limit or transient 5xx, pause with exponential backoff:
wait = min(max_backoff, base * 2^attempt + jitter).

3. Atomic Pre-Auth Locks

RSFlowHub acquires an atomic lock verifying base credits before model invocation. If validation fails, zero credits are deducted.

Request Body Parameters

Field Type Required Description
query string Required The raw user natural-language search string (Max: 5,000 characters).
schema object Optional Optional JSON object mapping field names to types, allowed values, sortability parameters to restrict generated filters.
context object Optional Optional JSON object defining business context (e.g. domain, default currency, timezone).
model string Optional Optional AI model to use.

How It Works

RSFlowHub performs search query parsing to structure parameters, but does NOT connect to your database or execute queries. Your application is responsible for executing the actual search against your search index (e.g., MySQL, Elasticsearch, Algolia, Meilisearch).

User Search
RSFlowHub API
Structured JSON Object
Your Search Engine

Core Capabilities

This API combines several NLP search capabilities into a single request:

  • Intent Detection: Identifies search category (e.g., product_search, job_search, property_search).
  • Query Normalization: Strips filter tokens to return clean, canonical search keywords (e.g., "men shoe running black" becomes "black men's running shoes").
  • Typo-Aware Rewriting: Standardizes obvious typos (e.g., "iphne 16 prm mx" becomes "iPhone 16 Pro Max") when confidence is high.
  • Entity Extraction: Identifies brands, locations, numeric values, etc.
  • Schema-Aware Filters: Restricts filters to fields and types defined in your custom schema.
  • Sorting: Detects sort direction and sort parameters (e.g., "highest rated first" -> {"field": "rating", "direction": "desc"}).
  • Multilingual/Mixed-Language: Understands queries in English, Hindi, Gujarati, Hinglish, and other mixed languages.
  • Exclusions: Understands negations (e.g., "except Samsung" -> {"exclude": {"brand": ["Samsung"]}}).
  • Relative Dates: Translates relative time expressions (e.g., "last 7 days") into absolute ISO dates.
  • Ambiguity Detection: Flags query ambiguity requiring user clarification.

E-Commerce Example

Here is an example passing e-commerce search queries with a defined schema configuration.

JSON Request
{
  "query": "Samsung 5G phones under 20000 with 8GB RAM, highest rated first",
  "schema": {
    "brand": {"type": "string"},
    "network": {"type": "string"},
    "price": {"type": "number"},
    "ram": {"type": "string"},
    "rating": {"type": "number"}
  },
  "context": {
    "domain": "ecommerce",
    "default_currency": "INR"
  }
}
curl-trigger.sh cURL
curl -X POST https://rsflowhub.com/api/v1/ai/search-query-parse \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "Samsung 5G phones under 20000 with 8GB RAM, highest rated first",
    "schema": {
      "brand": {"type": "string"},
      "network": {"type": "string"},
      "price": {"type": "number"},
      "ram": {"type": "string"},
      "rating": {"type": "number"}
    }
  }'

Example Response

The response returns intent, language, clean normalized query keywords, and structured schema-aligned filter operators.

response.json JSON Response
200 OK 118ms
{
  "success": true,
  "data": {
    "result": {
      "original_query": "Samsung 5G phones under 20000 with 8GB RAM, highest rated first",
      "normalized_query": "Samsung 5G smartphone",
      "intent": "product_search",
      "language": "en",
      "entities": [
        {"type": "brand", "value": "Samsung"},
        {"type": "ram", "value": "8GB"},
        {"type": "price", "value": "20000"}
      ],
      "filters": {
        "brand": "Samsung",
        "network": "5G",
        "price": {
          "lte": 20000
        },
        "ram": "8GB"
      },
      "exclude": {},
      "sort": {
        "field": "rating",
        "direction": "desc"
      },
      "is_ambiguous": false,
      "ambiguities": []
    }
  },
  "meta": {
    "credits_used": 2,
    "credits_remaining": 990
  }
}

Schema & Integration Guide

Provide a schema to guarantee that filters generated by the AI match fields supported by your application. If a field is not declared in your schema, it will not be returned in the filters or sort blocks. Supported types inside the schema include: "string", "number", and "boolean".

Example Integrations:

  • Jobs Search: Query: "remote Laravel jobs posted in last 7 days" -> yields {"filters": {"work_type": "remote", "created_at": {"gte": "2026-07-11T00:00:00Z"}}}.
  • Real Estate: Query: "2BHK flat for rent in Ahmedabad under 25k" -> yields {"filters": {"rooms": 2, "transaction_type": "rent", "city": "Ahmedabad", "price": {"lte": 25000}}}.
  • SaaS Dashboards: Query: "failed payments from last month" -> yields {"filters": {"status": "failed", "created_at": {"between": ["2026-06-01T00:00:00Z", "2026-06-30T23:59:59Z"]}}}.

API Request Example

Use the cURL snippet below to test the endpoint.

curl-trigger.sh cURL
curl -X POST 'https://rsflowhub.com/api/v1/ai/search-query-parse' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": "Samsung 5G phones under ₹20,000 with 8GB RAM, highest rated first",
    "schema": {
        "brand": {
            "type": "string"
        },
        "price": {
            "type": "number"
        }
    }
}'

Common Failure Modes & Troubleshooting Matrix

HTTP Code Error Code Root Cause Recommended Remediation
400 bad_request Malformed JSON syntax or missing required top-level parameters. Validate JSON payload with Content-Type: application/json and ensure all required fields are present.
401 unauthorized Missing, revoked, or incorrectly formatted x-api-key header. Verify API key exists in Dashboard → API Keys and pass in x-api-key or Authorization: Bearer.
402 insufficient_credits Account credit balance is lower than the base required credits (3 credits). Top up credits in billing settings or enable auto-recharge to prevent pipeline interruption.
422 validation_error Input failed parameter constraints (e.g., character length exceeded or invalid array types). Review parameters table above and adjust payload length, types, or structure accordingly.
429 rate_limit_exceeded Concurrency limit (60 requests/minute default) reached for this endpoint key. Back off and retry using the timestamp in Retry-After response header, or batch requests.

Technical Q&A (FAQ)

We recommend setting a client timeout of 5 to 8 seconds. While average latency is under 150ms, large input payloads or complex reasoning models may require additional processing time.

RSFlowHub uses an atomic pre-flight check. Before processing, the gateway validates that your wallet has at least 3 base credits. If the request fails validation (422) or is malformed (400), no credits are charged.

When a 429 is received, your application should respect the 'Retry-After' header and use an exponential backoff retry policy with randomized jitter to prevent thundering herd problems.

Every successful response returns { "success": true, "data": { ... }, "meta": { "credits_used": int, "credits_remaining": int } }.

Ready to build?

Create your free account and make your first API call in minutes.