This kinda sucks BUT I would take it over any Intuit API any day. They have a simple REST API that works exactly like you would expect. I assume if I really need more than 1000 calls a day I could probably contact them and get it raised.
It's 1000 api calls a day, right now we are in an early phrase and it is free. If you require more calls we can accomodate more calls based on your needs, and it would still be at no cost.
Something isn't well thought-out here. The pricing? The usage?
$49 per month for one million records, one million calls over the API and only 20(!) sessions. I don't think there's a consumer or business app that I could build that would stay under the session and call limits.
$17/mo is for 300 API calls per day - so that would be closer to 9,000 calls.
If you are looking to do more API calls than that there would definitely be cheaper pricing - especially if your use case involves sending requests as the user types!
Have you looked at the rate limits? They changed it from 60 calls per user per client ID to 100 calls per minute per client ID. Nothing is getting built with limits that low
Is there any good reads wrt the blowback on cost of the API? I've only read that it costs $0.25 per 1000 calls which seems relatively cheap, but I haven't looked into how it affects use cases.
The cost per question seems super high. I can't even think of an API where a single call would cost $1cent. You better have a good pricing model to follow up on this.
While he's suggesting $1 for 1000 calls, I find it interesting to suggest $1 per call for "anything" wouldn't be worth it... for example would you pay $1 to pull someone's credit report? (not that you need to, but just as an example where $1 per API call would actually be cheap).
this immediately made me think, don't the amazon API limits prevent one from making more than a few thousand calls an hour. Would be very interested to learn how you are countering that. I simply avoid doing anything with Amazon's product api just because of that reason.
reply