Querit Search API Enterprise

Querit Search API Enterprise provides web search for AI agents and enterprise applications.

POST <https://api.querit.ai/v1/search>

Use your Querit Enterprise API key as a Bearer token:

Authorization: Bearer YOUR_API_KEY Content-Type: application/json

API keys are available from the Querit API Key Management page.

curl --request POST '<https://api.querit.ai/v1/search>' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "query": "What is the latest progress on large language models?", "count": 20 }'

• query (string, required): Search query.
• count (integer, optional): Maximum number of results.
• filters (object, optional): Site, date, country and language filters. See the API reference below for supported values.

Successful JSON response example (result content and URLs are illustrative):

{ "took": "312ms", "error_code": 200, "error_msg": "", "search_id": 8842013, "query_context": { "query": "how vector databases handle hybrid search" }, "results": { "result": [ { "url": "https://example.com/post", "title": "Hybrid search explained", "snippet": "An overview of hybrid search.", "page_age": "2026-07-14T09:00:00Z", "site_name": "example.com", "site_icon": "https://example.com/favicon.ico" } ] } }

Response fields:

• took (string): Request processing duration.
• error_code (integer): Response code; 200 indicates success. Check the JSON error_code as well as the HTTP status.
• error_msg (string): Error message; empty in this successful response.
• search_id (integer): Search identifier for tracing and troubleshooting.
• query_context (object): Query context; query (string) contains the query text.
• results (object): Result container; result (array of objects) contains search results.
• Each result: url (string), page URL; title (string), page title; snippet (string), text excerpt; page_age (string), timestamp associated with the page; site_name (string), source website name; site_icon (string), website icon URL.

HTTP status codes and recommended actions:

• 400: Invalid request parameters. Check the request body and parameter values.
• 401: Missing or invalid authentication credentials. Verify the API key and authentication header.
• 403: Access is not permitted. Verify that the account has Enterprise Search API access.
• 404: Endpoint not found. Verify the /v1/search path and POST method.
• 429: Request rate limit exceeded. Reduce the request rate and retry with exponential backoff.
• 500: Internal server error. Retry with exponential backoff; contact support if the issue persists.
• 503: Service temporarily unavailable. Retry later with exponential backoff.

The documented error fields are top-level JSON properties. This JSON Schema describes the error-related fields; it is a schema, not an example response:

{ "type": "object", "properties": { "error_code": { "type": "integer", "description": "Error code" }, "error_msg": { "type": "string", "description": "Error detail" }, "search_id": { "type": "integer", "description": "Request identifier" } } }

Inspect error_code even on HTTP 200. Log search_id when available and send it to support without your API key. Correct 400/401/403/404 before retrying; use bounded exponential backoff for 429/500/503.

Note: Enterprise rate limits and quotas are plan-specific.

API reference and error handling: https://www.querit.ai/en/docs/reference/post-for-coding-agents  Website: https://querit.ai  Email: support@querit.ai