Noob Question while giving custom api call

Below is custom api request

i have validated the body parameters they are valid json but still n8n is giving json error

{ "status":"created",
"pickup_date_time":"2022-11-07 14:30",
"edd":null,
"add":null,
"mode":"surface",
"shipment_purpose":"commercial",
"no_of_packages":1,
"approx_weight":"45",
"invoice_value":115000,
"is_insured":false,
"remarks":"fragile items",
"eway_bill_no":"241504835550",
"invoice_number":"INV-2223070",
"chargeable_weight_carrier":45 ,
"source_warehouse_name":"Spinefit Medical Pvt Ltd",
"source_address_line1":"102 B Ujwal Sherene Baner",
"source_address_line2":"Near Mauli Garden","source_pincode":"411045",
"source_city":"Pune",
"source_state":"Maharashtra",
"sender_contact_person_name":"Spinefit Medical",
"is_to_pay":false,
"sender_contact_person_email":"[email protected]", "sender_contact_person_contact_no":"9569999953",
"to_pay_amount":null,
"destination_warehouse_name":"SNAS IOT LABORATORIES PRIVATE LIMITED", 
"destination_address_line1":"Asha Nikum ",
"destination_address_line2":"Asha Nikum ",
"destination_pincode":"456010",
"destination_city":"Ujjain ",
"destination_state":"Madhya Pradesh ", "recipient_contact_person_name":"SNAS IOT LABORATORIES PRIVATE LIMITED", "recipient_contact_person_email": "", 
"recipient_contact_person_contact_no":"9131073367", "delivery_partner":"gati",
"client_id":3174, 
"packaging_unit_details":[ {"units":1,
"weight":45, "length":125, "height":80, "width":45,
"unit":"cm"
} ], 
"recipient_GST":"27ABACS5190H1Z7", 
"label_url":"", 
"pod_url":"",
"source":"api", 
"volumetric_weight":"45", 
"lrn":"", 
"ship_date":"2022-11-07", 
"supporting_docs":["http://docs.google.com/document/d/1ugk5LNdGsQc9G5hCTWGUHuNw9_JwrGRWNcqwjCbR41Y/export?format=pdf","https://drive.google.com/uc?id=10ooLAihfimWLzi7z6-UOExV3gS_ddmRZ&export=download"],
"invoice_date":"2022-11-07", 
"shipment_type":"forward", 
"chargeable_weight_garud":45}

Hi @Spinefit, welcome to the community :tada:

I am sorry to hear you’re having trouble. It seems your workflow requires quite a bit of additional data to reproduce the problem you are having as your expression seems to reference fields from several other nodes. I suspect one of these values causes the JSON structure to break.

Perhaps you can consider defining individual fields in the HTTP Request node, like so?

This way, n8n should build a proper JSON structure based on the available data.

i have shared the final json data also which i checked it was valid json
but i dont knw some how it started showing error all of sudden

Which n8n version are you running @Spinefit? I tried running your example on [email protected] against a site not expecting any authentication and it completed just fine:

Also, have you tried setting the individual values over trying to manually build a valid JSON string? Did you get the same error with this approach?