Comments
-
The team is looking into this, but they're asking if you can share a little more context on the failure rate you're seeing. Specifically, you mentioned it "does not work in 80% of the times", but can you offer some more details on that? For instance, are you always seeing an 80% failure rate on these calls, or does it only…
-
It sounds like you're trying to use the Sign API, so you can reach the right people for help using this page: https://faq.hellosign.com/hc/en-us/requests/new
-
Dropbox does not offer this on the public API, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.
-
Thanks for confirming! We'll look into it and I'll follow up here with any updates for you.
-
Given that the access token no longer works even in the environment where it originally worked, it sounds like the access token was likely revoked. By default, Dropbox API access tokens for your app(s) don't become invalid and yield 'invalid_access_token' by themselves, but there a number of different ways that a Dropbox…
-
No, there isn't a way to retrieve the scope information programmatically. If you're the developer of the app, you can view and configure the scopes for the app on the app's page on the App Console. You can also specify a more specific sub-set of scopes to request programmatically using the 'scope' parameter on…
-
Thanks for following up. Unfortunately it appears the request ID is not actually getting set there for some reason. Can you confirm if you're performing these calls using an app owned by the Dropbox account you're using to post in the forum here? We can try to look up the failures that way instead.
-
La llamada a la API de Dropbox para cargar un archivo en una sola solicitud, /2/files/upload, admite la carga de archivos de hasta 150 MB de tamaño, por lo que debería poder admitir un archivo de 13 MB. Acabo de intentar cargar un archivo PDF de 50 MB usando ese punto final y se cargó correctamente. También pude leer el…
-
Thanks for the report. Can you share several request IDs (see here) for some of these failures? That would help us check on it.
-
Update: the timeout has been increased to 15 minutes.
-
Update: the timeout has been increased to 15 minutes.
-
When you using the files_download (or files_download_to_file) functionality, Dropbox will return the exact data that it has for the file. Dropbox does not modify the data that it receives when a file is uploaded, so if the embedded metadata is not present in the returned data, it means that it was not present when the file…
-
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:
