The Elasticsearch-compatible API
This API accepts a documented subset of Elasticsearch-style document and search requests. It is useful when an application already uses that request format. It does not provide a full Elasticsearch cluster or certify every client integration.
Start with the quickstart, then learn field mappings, search queries and bulk writes. Check availability and authentication first.
- Connect to the search endpointUse the dedicated interface and its supported client contract.
- Define and load documentsChoose field mappings and stable document IDs.
- Send a supported searchUse the documented query DSL for your question.
- Inspect matching hitsCheck IDs, returned fields and any aggregations.
What you point at it
Use a compatible Elasticsearch 7.x client or plain HTTP. The endpoint reports version 7.14.2. Use the complete tenant endpoint as the client base URL; each index lives under that path.
POST /v1/tenants/:tenant/es/:index/_search
PUT /v1/tenants/:tenant/es/:index/_doc/:id
POST /v1/tenants/:tenant/es/_bulkWhat makes it different from a search cluster
- Document writes and search use the same compatibility API. Start by writing a document, reading it by ID and searching an indexed field.
- Access depends on the request identity. Test the intended role and policies with the actual queries your application will send.
- Other query modes have separate interfaces. Vector indexing and cross-query result handling remain explicit application tasks. Do not assume an Elasticsearch write creates a vector embedding.
What it does not do
Coverage is limited to the documented API subset. Unsupported bodies can return errors, while unknown URL parameters are currently ignored. Check the supported options explicitly; HTTP success alone does not prove that every option was applied.
| Area | Answered | Refused, and why |
|---|---|---|
| Aggregations | terms, metrics, range, histogram, date_histogram, percentiles, top_hits, filters, sub-aggregations, pipelines, extended_stats | composite, nested have no executor yet; missing on a metric aggregation would fill in a value you did not choose |
| Suggesters | the term suggester, with suggest_mode | phrase and completion have no executor; popular ranks by a document frequency this API does not report |
| Paging | search_after, scroll and Point-in-Time | Check the deployment limits in /v1/capabilities |
| Scoring | function_score, per-field boosts | script_score and rescore would run arbitrary script |
| Cluster management | index create, delete, mapping, _field_caps, legacy and composable templates | ILM and snapshot administration are not supported over this API |
Vector and hybrid search live on their own surface — see querying.
Elasticsearch is a trademark of Elasticsearch B.V., registered in the U.S. and in other countries. OriginChainDB is not affiliated with, endorsed by, or sponsored by Elasticsearch B.V. OriginChainDB implements a compatible HTTP API so that existing Elasticsearch clients can talk to it; it does not distribute Elasticsearch software.