Existing integration loading files from specific path stopped working suddenly saying path not_found

[TalesCreator]

I had an existing dropbox API integration that had worked fine for a few years. We had not made any code change nor file / permission changes, and the integration abruptly started to return error of path "not_found" around June 20. However, I am able to see the file when I use the web-based interface.

Any help would be greatly appreciated!

[Здравко]

---

@TalesCreator wrote:

..., and the integration abruptly started to return error of path "not_found" ...

---

Hi @TalesCreator,

You may try do the same call using Dropbox API Explorer. Use the same parameters like in the application - i.e. use the same file id or path - whatever is in the code. What do you get there?

Good luck.

[TalesCreator]

Upon further examination; it appears that only files from older (e.g., 2022) are unable to be looked up via API while newer files (e.g., 2024-07-01) are able to be loaded fine.

[Greg-DB]

@TalesCreator Are you perhaps on a team that recently migrated to the team space configuration? Please note that by default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, the contents of the team space will not be found, and uploads will go to your member folder.

You can configure API calls to operate in the "team space" instead though, in order to interact with files/folders in the team space, if needed/desired. To do so, you'll need to set the "Dropbox-API-Path-Root" header. You can find information on how to use this in the Team Files Guide.

[TalesCreator]

I have been accessing a team folder as a member using these headers:

headers = {

"Dropbox-API-Select-User": "dbmid:Abcde...",

"Dropbox-API-Path-Root":'{".tag": "namespace_id", "namespace_id": "123456..."}',

}

dropbox.Dropbox(

oauth2_access_token="...",

oauth2_access_token_expiration=...,

oauth2_refresh_token="...",

app_key="...",

app_secret="...",

headers=headers,

)

Are you thinking that perhaps something happened to my team/member setup and the files are no longer being saved to the team folder?

[Greg-DB]

It sounds like your team may have migrated to the updated team space configuration. I see you were accessing a specific namespace ID, though that may be out of date.

There a number of different ways of using this functionality depending on what you want to do, but if you want to operate in your team space, I suggest using the "root" mode instead of the "namespace_id" mode. The Team Files Guide and Path Root Header Modes documentation covers this in more detail.