What is the maximum limit for fetching the facebook pages from an account?
Let's suppose if a facebook account has more than 200 pages to administer. If I try to retrieve facebook pages of that account using '/me/accounts' edge.
Then I get data as well as paging (containing cursors and next, previous page links). What I want to know is If I can set a limit while fetching the facebook pages like '/me/accounts?limit=200' and get all the 200 facebook pages the account has??
I have searched the documentation But there is no clear explanation as for this rate limit.
If you mean the API limit, it´s dynamic and not a definitive value. A general rule is "600 calls per 600 seconds, per token & per IP". You can also read this in other Stackoverflow threads, for example: What's the Facebook's Graph API call limit?
If you mean the limit parameter: Afaik they are changing it from time to time. I would not rely on it and just use the default value with paging, which is usually 25.
Related
Does the 'Per 100 seconds per user 20,000' limit apply to the user who uploads files to my account? that is, do they apply the limit through your ip? Or is it for me as the account holder?
I have an app where users upload files to my account, so I'd like to know if the limit applies to me as the account holder or the submitter to see if the app is viable.
There are two types of quotas user based quotas and application based quotas.
The last one Per 100 seconds per user Meaning A singe user of your application can make a max of 20k requests per 100 Seconds.
The first one Per 100 Seconds Meaning All users of your application at the same time may make a max of 20k requests per 100 seconds.
The middle one Per day Meaning all users of your application together can make a max of 1 billon requests per day.
Per user limits apply to anyone authorized to access your application, via the consent screen being shown to them. Its tracked by the access token they are using that contains the user info within it.
If you have the same user making requests over different ip address sometimes you can Hack the quota limit but it doesn't always work. A user is a user. No matter which machine they are coming from.
I am going to create a simple blog app which has included only reading facility (list/search/get). So, what is the quota limitation for reading in Blogger API? In my Quotas section which show as follows,
Queries per day 10,000
Queries per 100 seconds per user 100
I wanted know that what is the reading data quota limit from above stats?
10,000 request (list/search/get) per day; with the limit of 100 request per 100 second for each unique IP address.
These numbers are since, as stated here:
Depending on the API, Quota information may include requests per day,
requests per minute, and requests per minute per user.
Additionally, according to this you may modify these limits given your preference and performance, as well as monitor your API Usage following this.
I've suddenly started running into API limits. I've been restricting my API calls to: number of users * 200, but I'm getting error #4 about once per day.
This calculation was based on the docs from end of 2015 that said number of users your app had yesterday, plus new logins today.
But it looks like that has changed to:
The number of users your app has is the average daily active users of your app, plus today's new logins
Can someone explain to me what "average daily active users" is? And is there a way I can get access to this number?
Some information on what I'm doing:
My app fetches pages and posts from pages. To do this, I hit the Facebook API to get user's liked pages. Then each hour, I fetch posts from pages the system knows about.
I do the following:
Batch requests (50 per batch)
I'm only fetching posts since the last fetch (using since, until and limit params. 90% of the requests return 0 posts)
I'm only fetching posts from pages my users like
I'm using my app token for these requests
I limit the number of calls per hour to users * 200
Batch Requests don´t reduce API limits, they are only faster, that´s all. That being said: You wrote that you are using an "App Token" for the requests - you should use a "User Token" instead. It´s still a LOT of calls though, the only thing you can do in addition is to reduce the amount of API calls.
I found this endpoint in the documentation: https://developers.facebook.com/docs/graph-api/reference/application/
I tested this via
https://graph.facebook.com/v2.10/<my_app_id>?access_token=<my_access_token>&fields=daily_active_users
And it returned
{
"daily_active_users": "152",
"id": "<my_app_id>"
}
It is not average daily active users though
Does the Alexa API give a way to query Bounce Rates? There seems to be no ResponseGroup that returns this information. I've tried all the ResponseGroups and Actions mentioned in the documentation here.
There is no way to get highly accurate data via their API, but the alternative is to use SimilarWeb API for engagement data such as:
Average Page Views
Average number of page views per visitor
Average Time On Site
Bounce Rate
You can read more about the Engagement API in this link: https://developer.similarweb.com/engagement_api
I have an application where I want to show items that your friends have shared. This is basically a subset of data that would appear on your Facebook News Feed, so I am grabbing /me/home and then filtering out some things that I don't need.
The problem is that /me/home is extremely slow. I'm seeing a range of response times that is between 1200 and 10000 milliseconds with an average probably around 4 seconds.
Even with cached connections and a HTTP library that does SSL correctly these request times do not change much.
Does anyone know a better way to grab the News Feed? When I open Facebook in my browser, the News Feed appears pretty much immediately. So I am wondering if there is some Graph API call that is optimized for this data or has this result cached already.
Is there maybe an FQL alternative for this?
You can do this in FQL. This query should get you started:
SELECT post_id, actor_id, target_id, message, attachment FROM stream WHERE filter_key = 'others'
In the Graph API explorer on my feed, I get ~1000ms response times for the FQL query vs. ~2500ms for me/home.
For Facebook's home page, keep in mind that they use a series of AJAX queries to fill each of the boxes on your page a little at a time. I was on a very slow connection in a hotel last week and watched these fill box by box. The news feed fills first, five posts at a time, followed by the other boxes on the page. If page load performance could be an issue, you may want to move to an asynchronous model.
FQL will definitely help with that, as you'll be able to filter the data before it is returned by FB more finely than you can with just the Graph API.