API "wrapped" property all of a sudden

Hi Dev FS,

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with:

- the name and version number of the platform and SDK/library you are using, if any

- the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
- the full text of any error or unexpected output

Alternatively, you can open an API ticket with the above information using the following link: https://www.dropbox.com/developers/contact

the API version is 2. and here is the result output (some hidden for privacy).

When I test in Postman, the "wrapped" property never shows in body but "entries" element appears directly as expected.

However when it is operated in Microsoft PowerAutomate which I applied in the client system it has the "wrapped" as you see on the red line:

This above-mentioned connection I built is a custom connector I created. I checked the other flow connection provided originally by Microsoft, then they return properly without "wrapped" (the below is an example of their original connection of Dropbox "Create File") :

I hope this helps. Thank you!

D

Hi Dev FS,

Thank you for providing the additional information. If you are using our direct Dropbox API endpoints, the "entries" property would be an expected value to provide information about a file or folder.

That said, it sounds like you’re experiencing an issue with a third-party application (Microsoft Power Automate) using the Dropbox API. I would recommend reaching out to their support organization for further information related to the "wrapped" property in the response body.

If the developers of this app are having any trouble with the Dropbox API itself, they can reach out to Dropbox developer support directly with the relevant technical details.

Thank you iNeil !

As you said it makes sense if I see that is from Microsoft side. I posted in their community and while I have no response yet, I wish I could find any info like their updates or someone else who have the same issue. I'll still keep searching!