Greg-DB Dropbox Community Moderator

1. I see you're trying to call the /2/auth/token/from_oauth1 endpoint. It sounds like this is a new integration, so as Здравко noted, you should not be using that endpoint anyway. This endpoint is only meant for use if you already have pre-existing OAuth 1 access tokens. It should not be used as part of the OAuth 2 app…

The Dropbox API does not currently offer the ability to export .paper files as PDFs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

No, unfortunately the Dropbox API unfortunately doesn't offer the ability to search for files by date range like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

@"khatech" It sounds like you might be referring to shared link permissions. Check out the help center for more information on configuring shared link permissions. Otherwise, please share the rest of the requested details if you need technical support.

Its sounds like your team recently switched to the "team space" configuration. By default, API calls operate in the "member folder" of the connected account, not the "team space", so you wouldn't see anything in the team space when using the API by default. You can configure API calls to operate in the "team space" instead…

That should be controlled by your Podfile. For instance, v3.0.16 dropped iOS 8, so if you're still specifying support for iOS 8 in your Podfile, Cocoapods wouldn't upgrade you past that.

Can you elaborate on what you mean when you say it is "not working"? For example, what error or unexpected output or result do you get? Make sure you check the JavaScript console for any errors, for instance. Looking at the code you shared here, I don't see where "element" is defined. Do you have that defined? That needs…

Dropbox is in the process of switching to only issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh…

@"khatech" Can you elaborate on what you mean when you say "the shared link doesn't work"? For instance, please share: * the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s) * the full text of any error or unexpected output, a screenshot of the unexpected…

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: * the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s) * the full text of any error or unexpected output, a screenshot of the…

In that case, note that by default, shared links point to a HTML preview page for the file, but if you need direct file data access, you can modify the links as shown here.

@"khatech" Also, since you posted this in the API section, if you want to create a shared link programmatically, you would use /2/sharing/create_shared_link_with_settings. To retrieve existing shared links, use /2/sharing/list_shared_links. By the way, those are links to the documentation for the HTTPS endpoints…

There are a few reasons you may not be seeing everything. First, note that if your own app is registered for the "app folder" access type, it will only be able to access the contents of its own app folder, and won't be able to see the app folders of other apps. It's not possible to change the access type on an existing…

I recommend using the official Dropbox JavaScript SDK if possible, as it will do much of the work for you. Alternatively, it may also just serve as a good example even if you can't use it. Otherwise, refer to the documentation for /oauth2/token. It contains examples of calling the endpoint for different scenarios that you…

@"Petugo" Thanks for sharing the URL. Can you share which browsers (e.g., Chrome, Safari, and/or Firefox, etc.) and which version number(s) of each of those browser you're using where you see the issue?

You can download a zip of the SDK like that if you wish to work with it directly, e.g., to modify and build it manually, run the examples, etc., however to just use the package in your own application that is not necessary. In that case, it is generally recommended to just install it from NuGet (Dropbox.Api), e.g., using…

@"Petugo" What specific browser(s) and version(s) are you seeing this with? Some browsers/modes have special privacy/tracking blocking behaviors that may impact the Dropbox Embedder, since it's technically embedding a third party site.

Thanks for the report. It looks like this is a false positive on Apple's part. The only references to "showLoading" in the Dropbox Objective-C SDK are in a protocol we define and expose for callers to optionally implement and use. It sounds like this check may be inconsistent though. We suggest trying to upload again. You…

The "request body: could not decode input as JSON" error should indicate that the value you're sending in the request body couldn't be successfully parsed as JSON. In this case, that should be the value you have in the "data" field. Looking at that value, it seems the issue is that you have an extra \" at the end in \"\".…

@"Lansend" I don't have any news on this request, but thanks for the note! 

Thanks for the additional information. That's helpful. The extra portion you're seeing on the access token is a region suffix, which Dropbox will append in certain cases. The access token is still meant to be opaque, so the app should still just use the access token string as provided, including that suffix, if present.…

An access token shouldn't be immediately invalidated like that. It sounds like the access token string itself is somehow getting corrupted somewhere in the process. For reference, it sounds like you're getting an 'invalid_access_token' error, indicating that the supplied access token isn't valid. This indicates that the…

It is not possible to fully automate this process. This needs to be done manually by the user at least once. If your app needs to maintain long-term access without the user manually re-authorizing it repeatedly, the app should request "offline" access so that it gets a refresh token. The refresh token doesn't expire and…

@"Jay0203" Здравко is correct; changing an account's password does not affect any app keys, app secrets, access tokens, or refresh tokens for that account. Those can all be managed separately, e.g., via the App Console or Connected Apps page.

@"GIS_questions" As Здравко referred to, I recommend using the official Dropbox JavaScript SDK if possible, as it will do much of the work for you. Alternatively, it may also just serve as a good example even if you can't use it.

It looks like you're attempting to use a refresh token as a "Bearer" token in a few places in this case (where you set the "Authorization" header to "Bearer" + refreshToken). Refresh tokens themselves are not access tokens and cannot be used as Bearer tokens though, so please update your code to remove that. Refresh tokens…

This is now possible using the SearchOptions.account_id field on the /2/files/search_v2 endpoint.

Thanks for opening the ticket with the additional details. We'll follow up with you there shortly.

I just tried this out, and this functionality is working properly for me. Can you clarify what you mean when you say you've "verified the path that we are trying to access"? Also, I see you've redacted the path value anyway. If you'd prefer to share the troubleshooting details privately, you can open an open an API ticket…

Can you also share the options you're sending for the call, as well as show how you've "verified the path that we are trying to access"? Thanks in advance!