Child Item

Old dropbox and new dropbox API

Omri1984

Hi ,

i know that dropbox made a lot of changes in the last few years.

i want to understand something

there where a time that i needed to check the account , and check if the account is team in order to identify if it is a space team(new team) or the old one.

is this the case for today as well. or that dropbox deprecated all there old teams of the old dropbox and we move only to work with the new one?

i am using the api of dropbox and i used to support the old and the new dropbox themes.

can someone help me to understand 🙂

attaching the response from rootinfo

dropbox img.PNG

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

@Omri1984 The combination of the two features allows an app to distinguish between all three team configurations. Please refer to this post for information on that. The recommendation is use these feature values to programmatically determine how to handle any particular team, as described throughout that post.

All comments

Omri1984

i think maybe it is related to this .

https://dropbox.tech/developers/api-updates-to-better-support-team-spaces

And if yes can you do me some clearance here 🙂 ?

And if no please what is the issue ?

Greg-DB

While Dropbox is working to migrate teams to the updated team space, there are still teams on each of the different configurations.

And yes, the best resources for information on this are:

Omri1984

how can i request both of those featured values using the dropbox sdk with c# can share with an example of the code ?

Здравко

@Omri1984 wrote:
how can i request both of those featured values using the dropbox sdk with c# can share with an example of the code ?

@Omri1984, Take a look here and here. 😉

Good luck.

Greg-DB

@Omri1984 Здравко is correct; you can use those feature methods in the .NET SDK to make the feature calls for the team or user, but the team_shared_dropbox and distinct_member_home feature values for users and the has_distinct_member_homes feature values for teams haven't been implemented in .NET SDK yet.

You can determine the same information from the RootInfo object in your screenshot though:

team_shared_dropbox: this is the same as checking if the RootInfo is a TeamRootInfo.
distinct_member_home: this is the same as checking if rootNamespaceId
and homeNamespaceId are different.

Omri1984

Thank you @Здравко and thank you @Greg-DB i will give it a try.

In the past i implement changes that decided if it a new team or old by the root info.isteam
So now i have 3 options? New team old team and no team. And according to table i saw in article this is the way i need to decide if to use the team space client or the old client ??

Greg-DB

@Omri1984 Yes, there are currently three possible team configurations. The linked resources cover how to detect all of the different feature states so apps can use the features accordingly. Note though that the 'Dropbox-API-Path-Root' header is supported by all three configurations, so you can use that to set the root when calling for any account regardless of the team configuration if you wish to do so. That can make your code a bit simpler.

Omri1984

ok i am working on requesting the get values from the api,

just one more thing how do i know when to call the team.getvalues or user.getvalues

for old and new team should i use the team and for personal user i need to use the user ?

Omri1984

also trying to fetch the get values and getting an error such as

creating client with https://api.dropboxapi.com and a Bearer token

var requestBody = "{\"features\":[{\".tag\":\"\"distinct_member_home\"},{\".tag\":\"team_shared_dropbox\"}]}";

var content = new StringContent(JsonConvert.SerializeObject(requestBody), Encoding.UTF8, "application/json");
content.Headers.ContentType = new MediaTypeHeaderValue("application/json");

var res = await httpClient.PostAsync("/2/users/features/get_values",content);

but always get the same response of:

Result: "Error in call to API function \"users/features/get_values\": request body: expected object, got string"

am i missing something here

Здравко

Hi @Omri1984,

Why are you doing your life difficult and trying to rediscover hot water? 😯😀 That, what you're trying to figure out is already done in the official Dropbox .NET SDK and you can use it ready for use! 🤷 Why you don't you make your life easier? 😉

@Omri1984 wrote:
...
var requestBody = "{\"features\":[{\".tag\":\"\"distinct_member_home\"},{\".tag\":\"team_shared_dropbox\"}]}";
var content = new StringContent(JsonConvert.SerializeObject(requestBody), Encoding.UTF8, "application/json");
...
Result: "Error in call to API function \"users/features/get_values\": request body: expected object, got string"

am i missing something here

🙂 Maybe "missing" is not the exact word. Do you understand what JSON object means? What do you have in your requestBody variable? 🤔 Is that an object or some string what you later serialize? 🧐

Actually you have done something twice, not missing! 😉 That what the error message signals for.

By the way you are setting you content type twice. The second one:

@Omri1984 wrote:
...
content.Headers.ContentType = new MediaTypeHeaderValue("application/json");
...

... may be skipped since already exists in previous code statement.

Hope this drive you in right direction.

Omri1984

Bu greg wrote before that some of the parameters are not support by the sdk.

i need to support in my code all the options.

in the past we used the root.info.isTeam.

regrading the string of request body , it is a string that i am serializing it to an object

but now the root.info changed. so need to get the account value to determent what type of team / new team or personal the user is authenticate with

edit,

also I tried to remove the

content.Headers.ContentType = new MediaTypeHeaderValue("application/json");

but still got the same error

if you can show another way using c# also good 🙂

Здравко

@Omri1984 wrote:
...
regrading the string of request body , it is a string that i am serializing it to an object
...

Yes, you definitely have no any idea what JSON means. You CANNOT serialize string to object!!! You may rather serialize object to string and that's the idea of JSON and that's what it's used for actually. Learn more about JSON - it comes from javascript, but it's the same in all languages.

An easy thing, you can do, is to remove the serialization you have already done by hands actually.

Omri1984

@Здравко What i meant is that i am serialize it to a json object

This is the response after i removed the serialization

"Error in call to API function \"users/features/get_values\": request body: could not decode input as JSON"

Здравко

Hm...🤔 Did you by any chance exchange URI and content? Be more careful! 🙂

Take a look here how to order parameters and their format too. 😉

Omri1984

@Здравко this is all i am doing

var client = new HttpClient()
{
BaseAddress = new Uri(" https://api.dropboxapi.com"),
DefaultRequestHeaders =
{

}
};

client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken);
client.DefaultRequestHeaders.AcceptEncoding.Add(new StringWithQualityHeaderValue("UTF8"));

var requestBody = "{\"features\":[{\".tag\":\"\"other\"}]}";

var content = new StringContent(requestBody, Encoding.UTF8, "application/json");

var res = await httpClient.PostAsync("/2/users/features/get_values",content);

Здравко

@Omri1984, I don't know what you have done, but the above is definitely NOT the code you have used; it wouldn't even compile. There are errors inside - visible on first look on!

You can do something else though. Try to send request to a test site where you can see what actually you're sending (just type "test post requests" or something like in Google and select a site you prefer; not to advertise some). Once you have everything configured properly, just set the Dropbox endpoint back. Don't ask for every syntax error or similar you made. If needed pass a refresh course.

Greg-DB

@Omri1984 The team features tell you information about the entire team itself, and the user features tell you information about the specific user account (which may be a member of a team, and so there would be some overlap with the team features). Exactly which you use is up to you, depending on what you need to know in your app.

In any case, like Здравко mentioned, I do not recommend trying to re-implement these calls outside of the .NET SDK. If you're using the .NET SDK, I recommend continuing to use it as-is. While it does not have the new feature values implemented natively, you can use the root information returned by GetCurrentAccountAsync (like shown in your original screenshot) to determine the same things. Please refer to my earlier message for an explanation of the conditions to check.

Omri1984

Hi @Greg-DB

From the get current account i used to use in the past. It return is team = true when it was a new space team

But now it is changed.

Can please explain again how can i know if it is a bew team old team or user . And if it is a user if i can tell if it auser inside a old team new team or jist user with no team .

Please clear that for me 😁

Greg-DB

@Omri1984 Here's a basic example of how you can use the existing root information to determine the same information as the feature values using the .NET SDK:

var accountInfo = await this.client.Users.GetCurrentAccountAsync();

bool team_shared_dropbox = accountInfo.RootInfo.IsTeam;
Console.WriteLine("team_shared_dropbox: " + team_shared_dropbox);
bool distinct_member_home = accountInfo.RootInfo.RootNamespaceId != accountInfo.RootInfo.HomeNamespaceId;
Console.WriteLine("distinct_member_home: " + distinct_member_home);

Omri1984

Tjank you @Greg-DB

So the first one is the old team and the second one is?

Can you share an exmple for all the 3 option.
And can we call then old team new team(space)
And personal.
That will be very helpful.

I need to fix mu production app and the time is critical for me .

Greg-DB