Skip to content
RSFlowHub
Developer docs API v1 Stable OpenAPI SDKs Playground
Search Query Parse API Specification & Integration Reference

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
Typical Response 1-3 s
Client Timeout 15-30 s (recommended)
Provider Fallback Automatic
JSON Contract Envelope 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).

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
{
  "success": true,
  "request_id": "req_7f3a9c2d1e4b8a6f",
  "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": {
    "version": "v1",
    "timestamp": "2026-09-27T12:34:56+00:00"
  }
}

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"
        }
    }
}'

Want to try it without code? Test this request in the live Playground.


Common Failure Modes & Troubleshooting Matrix

HTTP Code Error Code Root Cause Recommended Remediation
401 API_KEY_MISSING / INVALID_API_KEY No key sent, or the key was mistyped or regenerated. Copy the current key from Dashboard → API Keys and send it as Authorization: Bearer (or X-API-Key).
402 INSUFFICIENT_CREDITS Your balance cannot cover the estimate for this call (base 3 credits plus input/output size). Buy a plan in Dashboard → Billing. Nothing was charged.
422 VALIDATION_ERROR A field is missing, too long or the wrong type, or the body is not valid JSON. Read error.details for the field messages and fix the request. Do not retry the same body.
429 RATE_LIMIT_EXCEEDED Your plan-wide or per-endpoint per-minute limit was reached. Wait the seconds in the Retry-After header, then retry with jitter. Rate limits
502 AI_PROVIDER_ERROR The AI model and its backup both failed. Retry with backoff and check the status page. Nothing was charged.

Technical Q&A (FAQ)

Each Search Query Parse API call costs 3 base credits, plus about 1 credit per 1,000 input characters and 1 credit per 500 output characters. Failed calls are not charged.

The query field accepts up to 5,000 characters per request. Larger inputs return a 422 validation error, so split long content into chunks.

Search Query Parse API runs on Google Gemini (gemini-2.5-flash), with automatic fallback to OpenAI (gpt-4.1-mini) if the primary provider fails or rate-limits. Models are tuned per task, so your integration does not change when we upgrade them.

Yes. Identical requests within 24 hours are answered from cache, which is faster and free or discounted in credits.

Most requests complete in 1 to 3 seconds; set a client timeout of 60 seconds so a call that switches to a backup model can finish. On HTTP 429, wait for the Retry-After delay. Retry network errors once or twice with exponential backoff and jitter.

Ready to build?

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

RSFlowHub

Sign in to continue

You'll come straight back to this page.

Forgot password?

New to RSFlowHub? Create a free account