Another beginners question:
I can get all eBay transactions from an item ID with GetSellerTransactions (XML).
I guess I can run cURL_multi and can get several transactions parallel. My question is, is there a limit how many item# I can send to the eBay API using cURL_multi?
eBay allows up to 18 simultaneous threads per AppID. See eBay Features Guide. This means you can fetch 18 transactions in parallel. But be aware that each single call still counts against the call limit of 5000 per day if your app hasn't passed the Compatible Application Check yet. Otherwise it will count against the 1.5 million calls per day limit.
Related
We are using Amazon affiliate Product Advertising API to fetch products from amazon. The account & API KEY was working when we implemented at first time till 1 month but after that we tried again for further project development it stopped working and always displaying below error:
AWS Access Key ID: XXXXXXXXXXXXXXXX. You are submitting requests too quickly. Please retry your requests at a slower rate.
Tried again and again. then finally we decided to create one more API KEY with same account but in this case on first attempt we again got same error.
After this we go to Amazon chat support but didn't find any specific solution. but they said
Each account used for Product Advertising API is allowed an initial usage limit up to a maximum of 1 request per second and a cumulative daily maximum of 8640 requests per day (TPD) for the first 30-day period after your account has been approved. Following that period, your PA API usage limit will solely be based on your shipped item revenue. Your account will earn a usage limit of 1 TPD for every 5 cents or 1 TPS (up to a maximum of 10 TPS) for every $4320 of shipped item revenue generated via the use of Product Advertising API for shipments in the previous 30-day period.
But now the problem is we are in the development stage and can't generate the revenue. also there is no Testing/Sandbox environment.
Looks like you have used all your usage limit for the account. So to make new requests you'll need to generate some revenue from your account.
I would advice you to test your product with a dummy API that generates the same response as PA API.
You may get some ideas from the tests written in this library: https://github.com/utekaravinash/gopaapi5
If you need more help you can go through this article to understand how API requests work: https://www.utekar.com/amazon-product-advertising-api-5-go-client-library-gopaapi/
Disclaimer: I'm the author of this open sourced library and it's written in Golang.
I'm in the process of devolving a new tool for a company app. The tool will be sending homogeneous number of searches to amadeus API. Is every search result is considered as a request? A sample search of a user will have to search the api 1000 times are these searches considered as requests? Because if the company has 10000 request limit per month it's going to be over by 10 users! I need to understand this please.
Every time you call an API (every time you use GET/POST verb) you do a "request".
The limitation (quota) is only in the test environment, you don't pay for it but you have a limited number of calls and you only have access to a subset of data.
In production, you don't have any limitation on the total number of queries you can do. You get access to our full set of data (live) but you pay per use (you pay for each request you do).
You have a limitation on the number you can do per second (TPS: 10 in production / 5 in test).
I have been searching for a while, but have not found any information on whether there are limits on calls to Amazon Rekognition service.
Does anyone know the numbers, or any source where I can look?
What I want to know is if they limit the number of calls allowed per minute or second. I'm looking for information on the the paid (not free) service tier.
You can find documentation on service limits for Rekognition at https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_rekognition.
The limits vary depending on which API you are accessing and from which region. Ex. DetectLabels has a limit of 5 transactions per second in US East (Ohio). You may request a limit increase on these numbers.
Here are the limits they have, at no time says anything about maximum number of requests per second as in other services
For example in amazon polly if it says the limits it has per second:
Any 2 transactions per second (tps) from these operations(DeleteLexicon, PutLexicon, GetLexicon, ListLexicons) combined.
Maximum allowed burst of 4 tps.
That's why I believe that it has no operations limit per minute, otherwise I would put it as they do in other services. I am using it to authenticate in the company where I am, that we are 23 and at the moment it has not given me any problems of operations per second.
References:
http://docs.aws.amazon.com/rekognition/latest/dg/limits.html
http://docs.aws.amazon.com/polly/latest/dg/limits.html
I have more than 600k products in my shopify store . the store is taking too much time to upload a products in admin back-end ( 11k product is taken almost 8 hours to complete the upload process )
I have even Used the "shopify product API" to add my product to store .
Even API is taking to much time to insert a product to store .
Now i am in big confusion that which i prefer to upload the product .
whether through "admin back-end" or "shopigy API call .
please suggest me a best way ..
thank you
If you have that many products you should either be looking at Shopify Plus or another platform entirely.
Each product takes one API call to upload and over time your API call limit averages out to 2 per second so 600k products with one variant per product would take 83 hours to upload. Your 11k products should only take 1.5 hours to upload though so unless you have a number of apps running there is something wrong with your API setup.
If you maximize the partition of your products into variants you can upload a product and its variants in a single call. Each product may have up to 100 variants so if you can group your products into variants the theoretical saving could be down to 6k API calls and just under an hour of processing (if you have variant images I think you'd need 3 calls per product/variant/image group - 1 to upload the products/variants/images; one to read the variant and image ids; one to assign the images to the variants.
Shopify Plus has 5 times the API limit (though I can't find an official confirmation of this) so your 600k products could be uploaded in 16 hours.
As #bknights said putting all the variants and combining products as variants is the fastest way.
I'd also like to add this: split your portfolio into lots and using API you can have parallel API calls running.
I have to update 60K variants on my store once a week. As I figured out it used take an entire weekend sometimes to finish of the things. I must add that I use PowerShell for this task. Later I came to realize that while one call is running my program is running idle and by trial and error I came to a conclusion that I can have 4 call made at 250 milli seconds gap each. So I update variants of all the products (each having around 45 variants) in a single call.
This way, the time cut down to less than 1/12th of the total time. Also you can use the API call limit returned by Shopify to calculate the time gaps further. For a non-Plus Shopify account this is the fastest way possible.
I've searched Google and the Twitter documentation for a very straightforward answer for how the following scenario would play out. Specifically, I'm wanting to understand how Twitter's rate limiting works on a "per user" and "per app" basis. Can someone take a look at the example below and explain to me what would happen. And please don't just refer me to a Twitter documentation URL! Thanks in advance.
Example:
The "GET friends/list" API call is currently limited to 15/user and 30/app within the 15 minute window (See https://developer.twitter.com/en/docs/accounts-and-users/follow-search-get-users/api-reference/get-friends-list).
If I have 4 users who all make the "GET friends/list" API call 10 times each within a 15 minute window (i.e. 40 calls made) does that mean I violate the 30/app limit? I'd still be within my limits for each of my 4 users, but do their individual calls eat away at the app limit too? Or is the app limit entirely separate and related solely to my app's token/secret?
The number of users (aka user tokens for your app that you've saved in your app store/config) give you that many times the specified per user limit (different for different APIs) for your app.
In your example, you're well within your limit if you make 10 calls per 15 minutes per user to the 'GET friends/list' API call since you have 60 (4 X 15) calls you can make per 15 minutes.
App limit applies if you don't have user tokens via user authZ/consent and are calling in application context only.
You should try your scenario with a 15 minute sleep after iterating over the 4 users and making 10 (upto 15) calls each in the user context (on the user's behalf) and you'll see that all works fine.