question Re: Jolt transformation based on unstable json format in Support Questions

Jolt transformation based on unstable json format

PeterKa — Mon, 03 Nov 2025 08:26:50 GMT

Hi, I am looking how to handle cases when json format may vary between different client responses. On response

{ "data": [ { "ID": "123", "Name": "Queen" }, { "ID": "456", "Name": "King" } ] }

we apply following jolt transform:

[ { "operation": "shift", "spec": { "data": { "*": { "ID": { "456": { "@(2,Name)": "Name" } } } } } } ]

but some times response is coming without leading "{"data":
and our transformation fails. So, generally, how can we query json with JOLT if we know for instance that Name and ID are next to each other somewhere in the structure?

Re: Jolt transformation based on unstable json format

vafs — Tue, 04 Nov 2025 16:44:26 GMT

Hello @PeterKa,

Thanks for reaching our Community.

For this, JOLT always need to have the values, it's not very much flexible if an expected value is missing.

But, something that JOLT offers is the default operation, that may help you to add "{"data": if it is already included.
You can see it here: https://lucabiscotti.github.io/jolt-guide.github.io/#default

That option may help you to have the needed format always before the shift.

Re: Jolt transformation based on unstable json format

DianaTorres — Wed, 19 Nov 2025 23:00:40 GMT

@PeterKa Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.

Re: Jolt transformation based on unstable json format

PeterKa — Thu, 20 Nov 2025 07:28:40 GMT

Generally, I agree with the comments and JOLT is not so flexible for this purpose. In my case I did it with multiple matches for various responses, but still format is needed. I will close the ticket, thank you Andrés @vafs