We are developing a mobile app where user can watch Vimeo videos which are being fetched via the Vimeo API but the problem is that when API request limit reaches above 100 from same IP it starts throwing a 'limit reached' exception.
We are using a Vimeo business account but still we are unable to find any solution or workaround to fix this issue.
Is there any workaround to overcome this problem?
What possible techniques we can use or implement (such as caching)?
One of the best solution is to optimize your API responses.
You can use a JSON filter to reduce the size of the responses.
Try to look at the Vimeo developer API
Related
Few days ago I was able to make request to:
https://drive.google.com/a/{{domain}}/file/d/{{docDriveId}}/image?pagenumber=1&w=400
Via this API I was able to get image preview on multi-page documents.
Seems it's there, but times-out after some time. It doesn't work anymore. Does anyone know what happened? It seems there's no documentation on this API.
On the other hand, I am aware of the thumbnailLink URL when getting document object via API, but this will only get 1st page preview.
Any alternative solutions to this?
Thanks a lot,
M
That URL is not a part of the official Drive API and is not guaranteed to remain stable. The Drive API doesn't include the ability to fetch per-page image previews of documents, but you may want to investigate using the embedLink as an alternative: https://developers.google.com/drive/v2/reference/files
When I use youtube video upload API on mobile phone it uploads the video but before redirect to the redirect_url, most of the times it throws this error:
url with error: http://uploads.gdata.youtube.com/action/FormDataUpload/FSVfvf45g45g4FFDSGSdfgr24g3t34t3EFVFFDSFGgg3435?nexturl=http://my-redirect-url.com:80/uploaded
This page cannot be loaded via the chrome data compression proxy. Try reloading this page.
when I just reload the page it redirects to the right redirect_url and the video is uploaded appropriately.
What might be a solution to fix this error?
I am the tech lead for the Chrome data compression proxy. We happen to have some special case logic to deal with YouTube URLs in the proxy which would cause this, but this seems not to be working as expected. Can you give me an example of your use of the API? Is this a POST request? Seems like something we should be able to fix.
Youtube or Google updated something in apps/youtube_api (unclear what) but when I accesses the app console it was different, then I created a new app and it worked.
Developing an AIR based app that captures video. The user will then be able to upload to facebook if they so choose.
Right now I am confused about the requirements in uploading videos to facebook.
Even though this is technically NOT a facebook application, will I need to create a Facebook application ID?
Will I also need to make use of the facebook-actionscript SDK?
I've read elsewhere that the API needs to launch the Facebook login within a web view.
Or are there alternatives in my case?
Even though this is technically NOT a facebook application, will I need to create a Facebook application ID?
Yes.
Will I also need to make use of the facebook-actionscript SDK? Or are there alternatives in my case?
Talking to the API works over HTTP – so you can use any technique that allows you to make HTTP requests.
But using a framework/SDK that already has methods for usual FB API stuff will be much simpler, than handling all that HTTP stuff yourself.
Is there any way to authenticate the application to use the Google Drive API without a native browser in an embedded system?
I'm looking for a solution to the user accepts and put your password and username using the OAuth2.0 without browser interactions... Is it possible?
My applications is build in Java Code.
Thanks in advance.
I am presently trying to do just this and I don't think it is possible because:
To authenticate in embedded device you need to use this process:
https://developers.google.com/accounts/docs/OAuth2ForDevices
the problem with this, is that it only accept limited range of scopes like:
--https://www.googleapis.com/auth/userinfo.profile
which works OK
but when you try with scope like:
--https://www.googleapis.com/auth/drive.*
you get invalid_scope.
If you find a solution please let me know, I have the same problem my device is embedded, has no screen, and is not available with remote desktop of the like.
thanks for any feed back.
Use the OAuth 2 device flow which is designed for cases where a browser isn't available on the device. It allows the user to complete the login & authorization on a separate, more capable device (phone/tablet/laptop) where a browser is available.
I'm using the google maps API v3 with flash and it works fine on one of my websites.
I transfered it to another website and changed the API key, but all I see is the default background color with no error message. Unfortunatly, I cannot access the flash source code.
Is there a way to debug the application or see some error messages without the source code?
Or maybe somebody has an idea of what is wrong?
Use Firebug Net monitor to see if all of the request are going through. That would be the first place that I would start. My guess is that there are HTTP Requests trying to get data from a domain that doesn't have a crossdomain policy allowing access from the new site you moved it to.
First of all maps V3 doesn't need a a key. I think you are combining parts of V2 (with key) and V3(which doesn't need key) so obviously there is something wrong in your code.