Error handling with /2/members/get_info and /2/team/groups/members/list

Thanks for writing this up!

For /2/team/members/get_info, this is the expected behavior. A successful call will return a list of MembersGetInfoItem, where each one is either id_not_found or member_info. Since this endpoint can accept multiple UserSelectorArg, the call itself will return an overall success with an id_not_found or member_info MembersGetInfoItem per input UserSelectorArg, so that it doesn't need to fail the entire call if just some of the input UserSelectorArg are not found.

For /2/team/groups/members/list, the expected behavior is the 409 with group_not_found. The 500 is a bug that I can reproduce, so we'll look into that. The 200 with an empty "members" list also isn't expected, but I can't reproduce that. Can you share a sample group ID value that gives you that? Thanks in advance! 

Yeah sure, here's more details:

The Dropbox Business environment that we use for tests purposes has 3 groups as shown in the admin console or via the /2/team/groups/list API call.

One of these groups has "group_id": "g:57460cd2e2edd1cd000000000000001a". If I call /2/team/groups/members/list on this group id I get, as expected, a 200 with the members listed under the "members" token in the response body.

If instead, I use g:57460cd2e2edd1cd000000000000001b (which is not one of my three groups), I get this response:

Status 200 OK

{
    "members": [],
    "cursor": "someCursor",
    "has_more": false
}

In fact, I can change pretty much anything in last 16 characters of the group id and I get the same empty "members" list.

Hope this helps

Hello Greg,

Just tested this and indeed I get a 409 every time, thanks for that. Strangely though, the body of the response is:

{
  "error": "No matching groups found for g:57460cd2e2edd1cd00000000000001b."
}

or 

{
  "error": "Some groups are not on the team."
}

Shouldn't it be in your standard format as specified in the APIv2 documentation?

{
  "error_summary": "to/no_write_permission/..",
  "error": {
    ".tag": "to",
    "to": {
      ".tag": "no_write_permission"
    }
  }
} 

 Thanks for your input.

Yep, you are right. My bad...