Greg-DB Dropbox Community Moderator

Si el archivo PDF no se puede leer, eso probablemente indicaría que los datos cargados no son datos PDF válidos. Sin embargo, Dropbox aceptará los bytes exactos para el archivo que cargue, independientemente del tipo de archivo. No modifica los datos que carga, así que asegúrese de cargar los datos exactos y correctos para…

It sounds like you're looking for other metadata embedded in image, such as using Exif. While the Dropbox API directly exposes information from some of these fields, as you found, it does not offer the ability to retrieve all of them, such as other fields like "description" and "caption". I'll pass this along as a feature…

It sounds like you're having trouble with the Sign API, so you can reach the right people for help using this page: https://faq.hellosign.com/hc/en-us/requests/new

It sounds like you're having trouble with the Sign API, so you can reach the right people for help using this page: https://faq.hellosign.com/hc/en-us/requests/new

The 'limit' parameter does not guarantee how many results will be returned per page. It only puts an approximate limit on the maximum number of entries that may be returned. Per the documentation: The maximum number of results to return per request. Note: This is an approximate number and there can be slightly more entries…

Update: this issue is still open with the team to investigate the degradation causing the transfer progress to stall. To help alleviate this though, we have increased the timeout to 15 minutes. Hope this helps!

I can't say off hand why that would be timing out, but given that it works locally it does seem like it is related to that lambda environment. I recommend referring to the support resources for the lambda environment to debug this, or to see if you can enable more verbose output at least. Unfortunately as that environment…

It sounds like you're having trouble with the Sign API, so you can reach the right people for help using this page: https://faq.hellosign.com/hc/en-us/requests/new

@"Polas" As Здравко said, for long-term access, you should request "offline" access to get a "refresh token". You can find more information in the OAuth Guide and authorization documentation, as well as this blog post. Also, it sounds like you may want to have multiple users connect directly to your own specific Dropbox…

It sounds like you're having trouble with the Sign API, so you can reach the right people for help using this page: https://faq.hellosign.com/hc/en-us/requests/new

From what I can tell from your screenshot, it looks like you're looking at the web page for a shared link for a file. In that case, you would use /2/sharing/get_shared_link_metadata to get information from the shared link. You can find all of the information available from that endpoint in the Dropbox API documentation for…

There isn't a delay, but note that scope changes are not retroactive. That is, if you enable a scope on an app, that does not retroactively add that scopes to existing tokens that were authorized before the scope was enabled. If the scope was enabled after connecting the app, the user would need to authorize the app again…

There are a few things to check here: * Make sure you're connected to the account that you mean to access. You can use GetCurrentAccountAsync to check the account for the access token you're currently using. * Is the access token you're using in that case connected to an app with the "app folder" access type? If so, note…

No, unfortunately the public Dropbox API doesn't offer that ability, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

That path would be considered "absolute", in that it's not relative to anything except the root itself. On the Dropbox API, there are multiple ways to reference items in a Dropbox account. Exactly how you do so is up to you, and will depend on how you want your application to work. You can find more information in the File…

While I can't provide support for Integromat itself or offer insight on what it does/doesn't allow, from what you've posted here at least it appears you have a new line before "url", which wouldn't be valid in an HTTP header. I suggest removing that and trying again.

@"StanR" Like Здравко found, it is also working for me in Firefox. What version of Firefox are you using, and are there any errors in the browser console on that page in Firefox for you when the Embedder doesn't appear?

@"StanR" What browser/version are you using? That page is working for me, showing the Embedder displaying a PDF file. Here's a screenshot of what it looks like in Chrome, for example:

You can find the instructions for using the Embedder here. There are working examples on that page, but as that is a page on the actual Dropbox web site, there is other code in the source, unrelated to the Embedder itself. To use the Embedder, you would need to: * Load the script as instructed under "Setting up the…

It sounds like you're referring to the team space upgrade. For reference, you can find more information on that upgrade in the help center here. On the Dropbox API, there are multiple ways to reference items in a Dropbox account. Exactly how you do so is up to you, and will depend on how you want your application to work.…

I'm glad to see you were able to resolve this already. For reference for anyone else coming across this, you can find the documentation for OAuth2FlowNoRedirectResult here and an example of getting the 'access_token' from it here.

If there are multiple changes at the same time in the same account or shared folder, you can run in to this 'too_many_write_operations' error, which is "lock contention". That's not explicit rate limiting and can't be increased or removed; it's a result of how Dropbox works on the back-end. This is a technical inability to…

@"mobilizer" Thanks for the note! I don't have any updates or other solution to add here, but I'll follow up if/when I do.

@"Hoteam Soft" Thanks for letting us know. @"alexlarocca" Yes, thank you for the note.

Migrating an app to scopes itself also doesn't change any existing access tokens, so users with pre-existing (non-scoped) authorizations would continue being able to upload files based on the previous broader authorization. In this scenario, only users that newly authorized the app with that insufficient list of scopes…

You can find information and examples of using that endpoint in the documentation here. This blog post may be useful as well. Make sure you're calling it correctly as shown. I just tried it and it is working for me. If something isn't working as expected for you, please share the relevant code snippet(s) and steps to…

That response should indicate that the file was saved successfully, so make sure you're looking in the right location when verifying that manually, e.g., on the Dropbox web site. For instance, check that you're signed in to the same account that you're connected to on the API (or at least, an account with the relevant…

A 'missing_scope' should just indicate that the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens. I'm not aware of anything that may have…

In order to get a refresh token, you need to request "offline" access when starting the app authorization flow, which you can do by setting 'token_access_type=offline' on /oauth2/authorize. You can find more information in the OAuth Guide and authorization documentation. There's a basic outline of processing this flow in…

If there are multiple changes at the same time in the same account or shared folder, you can run in to this 'too_many_write_operations' error, which is "lock contention". That's not explicit rate limiting and can't be increased or removed; it's a result of how Dropbox works on the back-end. This is a technical inability to…