API Introduction
Category : latest version
ElasticWarehouse defines its own API, however advanced users may want to use ElasticSearch API as well. We strongly recommend to use ElasticWarehouse API for any write operations (to make sure generated Json documents are in expected format). We have no objections to use ElasticSearch API for search purposes, especially transport client is more efficient than HTTP API. Each ElasticWarehouse API request can be transformed and debugged which may help with building your own search requests. If you need some search creiteria, let us know about them or share it on github.
| API type | Port | Description |
|---|---|---|
| ElasticWarehouse REST API | 10200 | Defines simple API to support most common file operations. Each request send to 10200 is being transformed into ElasticSearch request and subsequently executed on ElasticSearch cluster |
| ElasticWarehouse Grafana | 10500 | Grafana interface to visualize performance counters collected by ElasticWarehouse. Grafana interface is enabled in ElasticWarehouse embedded mode only. |
| ElasticSearch REST API | 9200 | See documentation on Elastic.co |
| ElasticSearch Transport client | 9300 | See documentation on Elastic.co |
| ElasticSearch Node client | n/a | See documentation on Elastic.co |