When I offer a deeplink into the Uber app: can a set a pick-up time in the future? E.g. two hours from now?
Thanks for expressing your interest in such a feature! We currently don't have a deeplink parameter to set up scheduled rides. However, we captured your interest and will consider it for future improvements.
Consider subscribing to our blog post for API updates. Thanks!
Related
My previous facebook developer account was blocked due I guess of making to many requests (No reason given by them and no answer after trying to contact them).
So before fall in the same issue with a new account. I would like to know if some has some relevant info or experience of how much request per second or hour can be made safetly to Facebook's API before been mark as abuse of service and been banned.
Thanks.
There is an article about rate limits in the official docs: https://developers.facebook.com/docs/graph-api/advanced/rate-limiting
I would like to set a link in a message to send to my uberEats customers that would take them to their apps last order where they could rate and tip the customer. Can this be done?
There is not currently an uberEATS API or public deeplink schema, so at this point this is not available. I believe deeplinks like you describe is something that the EATS team is interested in doing, however, so stay tuned in the second half of this year.
I'm trying to write a program that can retrieve the comments (as they happen) in my Facebook Live videos. Looking through the Docs I see the following text:
Reading Comments and Reactions
You can read live video comments by polling the Video Comment edge. In order to do this in the most efficient way so as not to exceed Graph API rate limits, we recommend receiving API updates via webhooks. You can also read live video reactions by polling the Reactions edge.
When I look at webhooks I can't seem to find any documentation that states how often they are called. Are they called on every comment, or at some pre-defined interval?
Also, webhooks callbacks run the risk of being received out of order. What's the best way to ensure that no messages are missed?
Thanks.
As of 3/7/2017 it is possible to be alerted about a comment posting via webhook but the comment itself are not sent in the request.
Apparently they updated their documentation. They dont suggest to use webhooks anymore for live comments. Now they suggest to use Polling. https://developers.facebook.com/docs/videos/live-video/production-broadcasts#comments
If the answer is yes, then what is it?
By maximum number of connectioned allowed per application I mean how many instances of the same api/key can be used to get the friends list at any one time, will Facebook block too many requests?
EDIT I have been looking at http://developers.facebook.com/ but have not been able to find the answer to my question there.
From their Policy
If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).
The only information I was able to find is something in a forum.
http://www.quora.com/Whats-the-Facebook-Open-Graph-API-rate-limit
After some testing and discussion with the Facebook platform team,
there is no official limit I'm aware of or can find in the
documentation. However, I've found 600 calls per 600 seconds, per
token & per IP to be about where they stop you. I've also seen some
application based rate limiting but don't have any numbers.
As a general rule, one call per second should not get rate limited. On
the surface this seems very restrictive but remember you can batch
certain calls and use the subscription API to get changes.
You can see how many API requests your users can have a day if you go to your Insights page and click on "Diagnostics". You can also see some other request statistics if you click on "Performance".
http://www.facebook.com/insights
Jeff Lindsay, who coined the term 'webhook', said that the difference between webhook and http callback is that webhooks are user-defined. I think I understand what he meant, but I was thinking about it and I asked myself, can webhooks be effectively used by regular users (I mean: non-developers)?
Usually people don't have a clue how the internet works, they don't know what http is, terms like URL, callback, or request-response don't say anything to them. I've heard that many people do not know the difference between a web browser and a web site, they think that internet really starts at google.com and they type in all urls in the google search box... I mean, what's the use of webhooks when you're not a developer?
Do you think services like AlertGrid make sense? It's a webhook consumer that you can configure to dispatch alerts (SMS, phone, email) either when the callback is NOT received in x amount of time, or when the received data meets user-defined condition, plus it does some data visualization. We wanted it to make webhooks usable for non-developers. But still it requires an initial integration by someone who at least knows how to configure the source to send the webhook events. In many cases it only takes pasting an url to a textbox, but it seems to be beyond the skills of a typical user.
So, are the webhook doomed to be used by software developers only, or is there a chance that millions of Facebook or Twitter users will start making use of them somehow?
I think that something implemented using Webhooks can be made very user friendly.
Suppose Stack Exchange allowed users to define a webhook that would be notified whenever you earned a badge. You could supply a custom URL, or there could be simple buttons to click that would set it up for your Facebook or Twitter account. It could be as simple as the Facebook Like button.
YES I think this is a great idea. It's actually something I designed in my head a couple months ago and didn't think the product existed.
Webhooks are extremely powerful and having a 'service bus' aggregate/manage/dispatch these callbacks is extremely compelling to me.
I think that we are a long way from the general public consuming webhooks in any sort of meaningful way but I don't see why not. I remember when RSS was a 'developer' only technology.
Thanks for the link. I'll be digging in more this weekend.