You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Extended Latin and 400 Bad Request
Hello,
I try to create a new member with name that contains chars of extended Latin alphabet (Ñ, Í, Õ etc.). I use powershell Invoke-RestMethod command and generate a body on the fly.
I receive "...
Thanks! That's the error from the API, and it does indicate that the issue is that the contents of the request body couldn't be successfully decoded as JSON.
It sounds like the issue is with encoding these characters. That's generally done automatically, but that doesn't seem to be the case with PowerShell/Invoke-RestMethod.
I'm not a PowerShell expert, and it also looks like copying it onto the forum didn't work right here, but I believe you need to additionally encode the body like this:
$enc = [System.Text.Encoding]::UTF8 $body = $enc.GetBytes($body)
Greg-DB
Dropbox Staff
Dropbox StaffI'm not too familiar with PowerShell, but it looks like you may be able to get the response body using the -OutFile option on Invoke-RestMethod.
Also, for reference, based on your code, you're using API v1, which is now deprecated. We recommend migrating to API v2 when you can. For example, the equivalent of /1/team/members/add is /2/team/members/add.
Anyway, "application/json" is the right Content-Type for these requests.
So, we have migrated to api v2.0 and still have the same problem.
$new_members = @(
@{
member_email = $mail
member_given_name = $groupMember.givenName
member_surname = $groupMember.surname
member_external_id = $keyFromAD
send_welcome_email = $true
}
)
$body = @{
new_members = $new_members
} | ConvertTo-Json
As a result $body refers to json-like string presentation of members to be created. If the one contains any char from extended alphabet it causes the 400 Bad Request response.
- Greg-DBFor API v2, the first step for debugging failures like this is also to check the content of the response body. It should contain a more useful error message. Can you share the response body? Also, since this is likely related to how the request body is formatted, please share a sample of that as well. Thanks in advance!
I captured a request and a response. I hide some sensitive info.
POST https://api.dropboxapi.com/2/team/members/add HTTP/1.1
{
"new_members": [
{
"member_email": "Baptiste.Bjaud@***",
"member_external_id": "ADSYNC ****",
"send_welcome_email": true,
"member_given_name": "Baptiste",
"member_surname": "B jaud"
}
]
}HTTP/1.1 400 Bad Request
Error in call to API function "team/members/add": request body: could not decode input as JSON
The name is Béjaud.
- Greg-DB
Thanks! That's the error from the API, and it does indicate that the issue is that the contents of the request body couldn't be successfully decoded as JSON.
It sounds like the issue is with encoding these characters. That's generally done automatically, but that doesn't seem to be the case with PowerShell/Invoke-RestMethod.
I'm not a PowerShell expert, and it also looks like copying it onto the forum didn't work right here, but I believe you need to additionally encode the body like this:
$enc = [System.Text.Encoding]::UTF8 $body = $enc.GetBytes($body)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
