An account_id value begins with the prefix "dbid" for an individual Dropbox account. In v2, we use account_id, which is a string that represents the user's unique Dropbox ID. Note: In v1, user accounts included a uid field, an integer that represented a user's Dropbox ID. The new endpoints do not have the /2 prefix, but rather, just begin with /oauth2. Some endpoints take different parameters or return different data make sure you check out the full documentation when that's noted. All v1 endpoints are listed in the left column, and the equivalent v2 endpoints are in the right column. Here's a mapping of how v1 functionality maps to v2. Update the error handling in your app to utilize v2 errors.Update your app's code, replacing API v1 calls with API v2 calls.Figure out which v1 endpoints your app uses, and look up the equivalent ones in API v2 using our v1 → v2 mapping table.Read up on the patterns of v2 endpoints, do a tutorial for an SDK, and test-drive v2 calls with your own data in the API Explorer. Familiarize yourself with the new v2 syntax.Check whether you need to migrate your user's access tokens or re-authenticate with a new permission.Note: In v1, there was a "Core API" with several SDKs, and a "Dropbox for Business API." In API v2, "the API" and "Dropbox Platform" refer to both of them it encompasses the endpoints for user and team apps. The following guide will help you migrate from API v1's "Core API" and "Dropbox for Business API" to API v2.
0 kommentar(er)
