RestAPI to Datalake storage

Hello @Nimai Ahluwalia and welcome to Microsoft Q&A.

I have been able to reproduce , or something very close to your situation. I believe the cause is improper mapping. Using the link you shared, I tried writing to a delimited text without mapping.
The results were

and then when I looked at the written output I saw

The output contains status: success
and message: Sucessfully! all records has been fetched.

These appear in the input, which I have abbreviated below.

[  
  {  
    "status": "success",  
    "data": [  
      {  
        "id": 1,  
        "employee_name": "Tiger Nixon",  
        "employee_salary": 320800,  
        "employee_age": 61,  
        "profile_image": ""  
      },  
      ...many records...  
      {  
        "id": 24,  
        "employee_name": "Doris Wilder",  
        "employee_salary": 85600,  
        "employee_age": 23,  
        "profile_image": ""  
      }  
    ],  
    "message": "Successfully! All records has been fetched."  
  }  
]  

Notice that the desired data is kept inside an inner structure, but what was written, were the fields in the outer structure. This can be solved by mapping like shown below.

The key piece here is the "Collection reference". Setting Collection reference to the response member which contains the collecion of data you want, makes it treat each child item as a record.

Now when I debug, I get:

Do not worry about the discrepancy in bytes read vs bytes written. This is a result of all the extra characters in JSON notation ({ : } ) not being needed in delimited text format. You can see the data is now written.