I can't find my answer so i'm asking you. I was wondering if pagination calls using "next_link" with OneLogin API would count as a call for the limit ?
example :
If I have 300 000 users to fetch from the API every 30 minutes. I would have to make (300 000 /50) 6000 calls using pagination (limit for an account is 5000/hour).
PS: maximum user per query is 50.
Thanks un advance for you answer.
After testing, the pagination call count as "a call". So limit apply for each call even using the next_link of pagination.
Pagination counts as a call.
But to solve the underlying issue, if your account is a large one (if you have 300K users, it sounds like it is) contact your customer success contact.
That 5K/hour limit is the default but it can easily be raised for large customers.
Related
I have a BQ query which returns around 25K records as of now and I want to apply pagination to it to fetch it in chunks of 1000.
Based on this link I can add BQ pagination by setting the maxResults property and use pageToken to get the next set of results.
I know that I add my own logic and use LIMIT and OFFSET but as per the documentation the billing will be for all the rows and not only the number of rows that are fetched
Applying a LIMIT clause to a SELECT * query does not affect the amount
of data read. You are billed for reading all bytes in the entire
table, and the query counts against your free tier quota.
But I can't seem to find any documentation which gives me a clear idea whether using maxResults property will actually reduce the amount of data that I'm billed for.
Can anyone please advice? Thanks in advance.
First of all i am very sorry because this question could appear nonconstructive or too localized to some moderators
I am just confuse with custom search API query limit's as i have read that it is free upto 100 queries and charge $5/1000 queries up to 10,000 i just want make me sure on this.
1) Is this limit for API call lets take an example i.e. I search with a keyword 'watch' and it returns 2000 results to me with only first 10 results in the object this is my first API call and when i again call the API for next 10 results it is going to make another API and count it 2 query out of 100 free?
Please read the above questions carefully i just want to know that reading through the pagination will make query quota to exceed the limit?
Each API call is counted as 1, so if 2 pagination requests are made they are 2 calls.
I was wondering what the limits were on the number of metafields that an entity in Shopify could have. For instance, under a given namespace for a product object, could you have 1000 unique key value pairs? Is there a hard limit?
Please note I have consulted the documentation on Shopify's Metafield API page (http://api.shopify.com/metafield.html) but it only states the following limits:
The namespace has a maximum of 20 characters, and the key has a maximum of 30 characters.
Thanks for help!
There's no hard limit, but if you're storing that much info you might want to consider doing it locally as retrieving it will become a pain.
The most metafields that we've applied to any given element to date is 5434. We have a collection that currently contains that many metafields, and it seems to be working fine!
I wouldn't advise doing this, as it's a nightmare to find and remove any via Postman if manual intervention is required. But it's certainly possible!
If you had the following
MyNS.Key1 = 1
MyNS.Key2 = 2
...
MyNS.Key1000 = 1000
You should be able to access it like
products.metafields.MyNS[someKey]
So not too difficult to retrieve, or am i missing something else
I was reading an article here and it looks like he is grabbing the IDs by the 100s. I thought it was possible to grab by 5000 each time?
The reason I'm asking is because sometimes there are profiles with much larger amounts of followers and you wouldn't have enough actions to do it all in one hour if one was to grab it by 100 each time.
So is it possible to grab 5000 ids each time, if so, how would I do this?
GET statuses/followers as shown in that article has been deprecated, but did used to return batches of 100
If you're trying to get follower ids, you would use GET followers/ids. This does return batches of up to 5000, and should just require you to change the URL slightly (see example URL at the bottom of the documentation page)
I have been trying to get the full list of playlists matching a certain keyword. I have discovered however that using start-index past 100 brings the same set of results as using start-index=1. It does not matter what the max-results parameter is - still the same results. The total results returned however is way above 100, thus it cannot be that the query returned only 100 results.
What might the problem be? Is it a quota of some sort or any other authentication restriction?
As an example - the queries bring the same result set, whether you use start-index=1, or start-index=101, or start-index = 201 etc:
http://gdata.youtube.com/feeds/api/playlists/snippets?q=%22Jan+Smit+Laura%22&max-results=50&start-index=1&v=2
Any idea will be much appreciated!
Regards
Christo
I made an interface for my site, and the way I avoided this problem is to do a query for a large number, then store the results. Let your web page then break up the results and present them however is needed.
For example, if someone wants to do a search of over 100 videos, do the search and collect the results, but only present them with the first group, say 10. Then when the person wants to see the next ten, you get them from the list you stored, rather than doing a new query.
Not only does this make paging faster, but it cuts down on the constant queries to the YouTube database.
Hope this makes sense and helps.