nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

What is expected behavior when specifying X-Dropbox-Perform-As-Team-Member but with token that d ...

Conrad H.1

oes not have team privilege?

I'm using the REST API to create a folder using an ordinary token for a user, but also passing X-Dropbox-Perform-As-Team-Member to operate on another user's account. So this should probably fail with an error. Instead, it seems to be creating the folder in the first user's account. Is that expected behavior?

Find more posts tagged with

API

Abuse

Comments

Greg-DB

I believe if you're making an API call in a context where that header doesn't apply, e.g., using the Core API with a normal user access token as you describe, the extra header will just be ignored. That is, the API only looks for that extra header when necessary, so what you describe is the expected behavior.

Conrad H.1

Thank you so much for the quick response. It confirms what I am seeing.

If you're interested in feedback, I have to say this is an unexpected design choice. Normally I would expect that if I tell a REST API "do X", and I give it an Authorization header which doesn't authorize that action, I would receive an error.

Zaowe Z.

ممتاز ومميز