# YAML payload parsing

**URL:** <https://forum.inductiveautomation.com/t/yaml-payload-parsing/49103>\
**Category:** General Discussion\
**Tags:** ignition80, scripting\
**Created:** [July 22, 2021, 5:19pm UTC](https://forum.inductiveautomation.com/t/yaml-payload-parsing/49103 "2021-07-22T17:19:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 22, 2021, 5:36pm UTC](https://forum.inductiveautomation.com/t/yaml-payload-parsing/49103/2 "2021-07-22T17:36:31Z")

</div>

The 'right' way to do it would be to create a custom module that brought a Java YAML parser into scope - it looks like the two main candidates are Jackson or 'snakeyaml'.  
The 'easy' way to do it would be to use the 'hack' described here:

> [@Importing and using 3rd party Java jar libraries in Ignition](https://forum.inductiveautomation.com/t/importing-and-using-3rd-party-java-jar-libraries-in-ignition/11342/3):
>
> For gateway-only access you can also just drop jar files into the lib/core/gateway folder (and then restart). Just don’t expect these to be part of any backups, available outside gateway scope, or available on another Ignition gateway unless you put them there also. Basically, you need to remember that you added those jars, else your project may someday stop working because you’ve found yourself running on an installation that does not have them.

If you drop the snakeyaml .jar file in the right location, the gateway will automatically load it to the classpath on the next restart, which will then make it available from scripting.

---

_[View the full topic](https://forum.inductiveautomation.com/t/yaml-payload-parsing/49103)._