Greetings;
I'm writing a script to export objects from ION Desk (via APIs in IONAPI) as a backup. I would like to also use this as a Version Control System moving forward to be able to look at changes to various objects in ION Desk over time.
The first thing I've found is the various endpoints for the APIs are not using the same syntax for various things like timestamps. Some endpoints don't even have last modified timestamps, so I'm having to pull the same transactions every time. This is kind of disappointing from a standards view point.
The real question I'm hear to ask is, why the format is different. When I pull the objects via the API, the format does not match what happens when I export them from ION Desk by hand. One is a JSON object, the other being XML. The exports from the APIs cannot be imported back in to ION Desk using the normal import, as the format is wrong.
Is there an undocumented option I can use to get the exports from the APIs to match what I get from ION Desk when I export an object?
Is there a way to get the JSON to be consistent when generated from the API? It seems that even with no changes, ION Desk randomly moves sections of the JSON around during export. It's the same object, same end results, but sections are placed at random during generation. I know this doesn't effect the function of the JSON, but it makes applying version control for tracking the real changes between versions almost impossible.
Thank for any help;
Billy