Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Using API in Salesforce with Named and External Credentials and OAuth2 upload OK but call to file sh
I have setup OAuth2 in Salesforce along with Named Credentials and External Credentials. I am calling the File Upload API in the code..that works fine with all the above. I setup a second Named Cred...
To answer your additional questions:
1. The access token generated in the app is not permanent, it does expire.
2. Could you expand on what blocks you may be encountering as far as wanting to "chunk load larger files"?
>>> I actually got that working OK.
3. Could you also further explain what you mean by "getting a second token on a second HTTP callout is a problem when calling the different API"?
Its just not clear to me what was causing the missing scope on the sharing call after the initial call to file upload.
So do you recommend going back the the Oauth access vs the token.
DB-Des
Dropbox Community Moderator
Dropbox Community Moderatorbossgolfer, It is recommended to get an access token via an OAuth flow, yes.
Keep in mind that access tokens, whether obtained from the app within the App Console or via OAuth flow, will eventually expire. The expiration time can be confirmed in the property expires_in, which is found in the response object returned from the /oauth2/token endpoint.
I hope this information provides more clarity!
Thanks. I went the route of Auth Provider plus Named and External Credentials in Salesforce and all is working well.
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
