# REST API Saved Objects attribute set?

**URL:** <https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986>\
**Category:** Kibana\
**Created:** [September 18, 2018, 12:58pm UTC](https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986 "2018-09-18T12:58:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shoffmeister](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shoffmeister/32/36086_2.png) [@shoffmeister](https://discuss.elastic.co/u/shoffmeister)\
**Post date:** [September 18, 2018, 12:58pm UTC](https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986/1 "2018-09-18T12:58:14Z")

</div>

I am successfully using [https://www.elastic.co/guide/en/kibana/master/saved-objects-api.html](https://www.elastic.co/guide/en/kibana/master/saved-objects-api.html) to create a default setup for Kibana, posting something as trivial as

[{  
"type": "index-pattern",  
"attributes": {  
"title": "file\*",  
"timeFieldName": "@timestamp"  
}  
}]

Is there any documentation on the set of attributes that can be set?

I realize that I could "do something", then export it, inspect it, tweak it ... Is there a more formal path?

My use case is that I want to cycle an environment - including ELK - in a fully automated fashion. Right now, I am looking into delivering the best possible Kibana experience after a docker-compose up.

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [September 18, 2018, 3:25pm UTC](https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986/2 "2018-09-18T15:25:59Z")

</div>

Hello,  
There is no documentation currently for the shape of the documents per type. I suspect that will come in the future when we add per type validation.  
Also this might be of some interest to you [https://github.com/elastic/stack-docker](https://github.com/elastic/stack-docker) -- an inspiration for running the stack with docker compose.

Cheers  
Rashmi

---

<div class="post-metadata">

**Author:** ![brainsage](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brainsage/32/36072_2.png) [@brainsage](https://discuss.elastic.co/u/brainsage)\
**Post date:** [October 2, 2018, 12:19pm UTC](https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986/3 "2018-10-02T12:19:26Z")

</div>

> [@shoffmeister](#):
>
> I am using [https://www.elastic.co/guide/en/kibana/master/saved-objects-api.html](https://www.elastic.co/guide/en/kibana/master/saved-objects-api.html)[essaywriter](https://hireessaywriter.org/) to create a default setup for Kibana, posting something as trivial as
> 
> [{  
> "type": "index-pattern",  
> "attributes": {  
> "title": "file\*",  
> "timeFieldName": "@timestamp"  
> }  
> }]
> 
> Is there any documentation on the set of attributes that can be set?
> 
> I realize that I could "do something", then export it, inspect it, tweak it ... Is there a more formal path?
> 
> My use case is that I want to cycle an environment - including ELK - in a fully automated fashion. Right now, I am looking into delivering the best possible Kibana experience after a docker-compose up.

Hi  
How can I use the Kibana Migration Assistant to migrate to Kibana 6.1.3? Tried to use the command `curl -XPOST -H "Content-Type: application/json" -H "kbn-xsrf: true" localhost:5601/api/kibana/settings/defaultIndex -d '{"value": "your-index-id"}'` but it failed.

Thanks,  
David

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 30, 2018, 12:19pm UTC](https://discuss.elastic.co/t/rest-api-saved-objects-attribute-set/148986/4 "2018-10-30T12:19:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.