* Adds collections landing page configuration and navigation header linking Signed-off-by: Aaron Stephanus <[email protected]> * Removes unnecessary collection property from the configuration. Signed-off-by: Aaron Stephanus <[email protected]> * Adds links to navigation collection headers to collection index pages based on the collection name Signed-off-by: Aaron Stephanus <[email protected]> * Hide index pages from view and add info to formatting guide Signed-off-by: Fanit Kolchina <[email protected]> --------- Signed-off-by: Aaron Stephanus <[email protected]> Signed-off-by: Fanit Kolchina <[email protected]> Co-authored-by: Fanit Kolchina <[email protected]>
531 B
531 B
layout, title, nav_order, has_toc, nav_exclude, redirect_from
| layout | title | nav_order | has_toc | nav_exclude | redirect_from | |
|---|---|---|---|---|---|---|
| default | REST API reference | 1 | true | true |
|
REST API reference
OpenSearch uses its REST API for most operations. This incomplete section includes REST API paths, HTTP verbs, supported parameters, request body details, and example responses.
In general, the OpenSearch REST API is no different from the Elasticsearch OSS REST API; most client code that worked with Elasticsearch OSS should also work with OpenSearch. {: .tip }