(API Execute) Different JSON Format With Same Set up?

[Ryan.Macromarketing]

Your Task History ID

IjU3NmQwNTY4MDYzMzA0MzM1MjZkNTUzMTUxMzI1MTY3NTQzMiI_3D_pc

Good day all,

We have something strange happening with a filtering sequence we're running

Below is a the proper format that our CRM receives the JSON

Where as this payload for our HAMILTON location comes with a different format (this is what we're trying to fix)

This has happened on a number of leads for the same location - the payload structure and format is seemingly set up the same so we're looking for an answer as to why the API posts are sent in a different format

Thank you all in advance,

Ryan M

 

[ArshilAhmad]

Hi @Ryan.Macromarketing,

Could you please state whether this change in payload structure results in the post being made in a different manner on your application?

 

[Ryan.Macromarketing]

Hey @ArshilAhmad , that's correct - our CRM is not receiving the lead information when the post is structured in this way

 

[ArshilAhmad]

Thank you for the update. Please allow us some time to look into this concern. We will get back to you with an update soon.

 

[Ryan.Macromarketing]

Thank you, looking forward

 

[ArshilAhmad]

The issue seems to be related to a missing double quote in the 'Time' field of your JSON in the Hamilton route. We have added the double quote on your behalf. We suggest that you test it on your end.

 

[Ryan.Macromarketing]

That's great thank you for your help