We are currently working on integrating the Job Order module with the Cut Plan software for our cutting machines. While we have the Tuhund API documentation, we need a small clarification regarding the available JSON data export options. There are two buttons: one labeled "Export JSON" and the other "Raw Data." During the integration phase, which of these should we use as the reference sample? Although both seem identical, what is the difference between these two options? Which data will the Job Order API return?
The Job Order Details API will return the exact same data as the "Export JSON" button. This is a comprehensive dataset, containing details about products, materials, bills of material, resources, timelines, production lines, production stages, status updates for each entity, and more. You can use whichever parts are relevant to your needs.
The "Raw Data" button, on the other hand, provides only the data that was originally entered into the system through the Job Order Register API. This data is immutable, serving as an unaltered record of the payload from the API call made by a third-party system to create the Job Order in Tuhund. It cannot be modified.
In contrast, the "Export JSON" data is dynamic and continues to update until the Job Order is completed. In some cases, such as when expenses are recorded later or invoices arrive after the fact, this data may even update after the Job Order has been closed.
The "Raw Data" is useful if you're pushing Job Orders into Tuhund via API. Since you're not using that process, you can disregard the "Raw Data" button.
