# JSON Components

**URL:** <https://forum.inductiveautomation.com/t/json-components/21255>\
**Category:** Ignition Early Access\
**Tags:** scripting\
**Created:** [December 6, 2018, 1:10pm UTC](https://forum.inductiveautomation.com/t/json-components/21255 "2018-12-06T13:10:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joostjojo](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@joostjojo](https://forum.inductiveautomation.com/u/joostjojo)\
**Post date:** [December 6, 2018, 1:10pm UTC](https://forum.inductiveautomation.com/t/json-components/21255/1 "2018-12-06T13:10:58Z")

</div>

Since components actually are JSON objects.  
Is it possible to create components and convert and send them to ignition perspective with an Web API?

example:  
I create an C# MVC WebAPI where I create a JSON component.  
I send the JSON trough an HTTP request to Ignition perspective.  
Does this see the JSON as a component?

---

<div class="post-metadata">

**Author:** ![David.Reed.Schmidt](https://avatars.discourse-cdn.com/v4/letter/d/5f9b8f/32.png) [@David.Reed.Schmidt](https://forum.inductiveautomation.com/u/David.Reed.Schmidt)\
**Post date:** [December 6, 2018, 2:29pm UTC](https://forum.inductiveautomation.com/t/json-components/21255/2 "2018-12-06T14:29:18Z")

</div>

Likewise is there a component that will allow the json object to render much in the same way as cut and paste on the screen. In other words a component that takes the entire json object as a binding. This way I can store the component in a database. When I want to tender it on the screen I can bind to a simple query like “select json where id=1”

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [December 6, 2018, 4:56pm UTC](https://forum.inductiveautomation.com/t/json-components/21255/3 "2018-12-06T16:56:51Z")

</div>

We have some loose ideas for a special view type that would act much like a WebDev python endpoint, meaning that the view’s definition (the JSON you’re talking about) would be calculated on the fly via a python method. I think this would be the best way to accomplish what you’re both talking about. No ETA quite yet, as it’s quite an advanced use case.