# Kibana 5.0 Ingest API

**URL:** https://discuss.elastic.co/t/kibana-5-0-ingest-api/65043
**Category:** Kibana
**Created:** [November 4, 2016, 6:40pm UTC](https://discuss.elastic.co/t/kibana-5-0-ingest-api/65043 "2016-11-04T18:40:25Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [November 23, 2016, 2:57am UTC](https://discuss.elastic.co/t/kibana-5-0-ingest-api/65043/5 "2016-11-23T02:57:12Z")

</div>

Hi @j9s3 and @ogibayashi,

Yes, if you are looking to _programatically_ create index patterns, the best approach at the moment is to modify the contents of the `.kibana` index directly via the Elasticsearch REST API. You can read a bit about the structure of the `.kibana` index here: [https://www.elastic.co/blog/kibana-under-the-hood-object-persistence](https://www.elastic.co/blog/kibana-under-the-hood-object-persistence)

**Fair Warning** : Modifying the `.kibana` index is, of course, not ideal because the index is meant to be an implementation detail of where Kibana stores its objects (index patterns, visualizations, etc.). It's possible the Kibana developers might change something about the structure/semantics of the documents in this index and that would break your script that's programmatically writing to this index.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-5-0-ingest-api/65043)._