Note that Dropbox users may revoke API authorizations (as described here) - so this error may suggest the end user unlinking the app in Dropbox (but not uninstalling your app or unlinking through it). These may also be due to temporary suspension, such as an administrator suspending a member within a Dropbox business team.
These errors are due to the bearer token of the associated request being invalid, expired, or lacking sufficient permission to perform the associated API call. Responses with 400 error code indicate an issue with the request itself, and thus will not be resolved by retrying them. For example, a Business application with Team Member Management attempting to use an endpoint requiring Team Auditing permission. These errors may also occur from attempting to access an endpoint unavailable to a given app type. Neglecting to sanitize input from end users, for example, would result in this. A common cause of this is malformed JSON request bodies, or JSON that does not conform to input fields and validation.
0 kommentar(er)
