Hey guys, question about the API:
Using the download-purchase API endpoint (which retrieves a download URL for the user) seems to count toward the file download limit, even if the file is never actually downloaded. I’m wondering if anyone can confirm that, if that is the intended functionality, and what is the best way to avoid hitting that limit.
I’m trying to provide my customers direct access to their plugin download package via the Envato API. I have been testing with a purchase code and API key, and using this endpoint:http://marketplace.envato.com/api/v3/USERNAME/API-KEY/download-purchase:550e8400-e29b-41d4-a716-446655440000.json
The result set looks like this:
This was working great. I only ever actually followed the download URL and downloaded the file once (just to test it was working). After that, I explicitly never downloaded the file, specifically because I knew there were limitations on how many times I could do so.
However, after testing for a while, it suddenly stopped working, and returning a message that the download was not currently available. Checking the Downloads page for that account, I saw the message that I’d exceeded 20 downloads in 24 hours, and the download was temporarily disabled.
I didn’t actually download the file 20 times, but I bet I hit the API requesting a download link 20 times.
So here’s the issue:
It seems that just hitting the purchase-download end point, even without ever downloading the file, counts toward the file limit
So here are my questions:
1. Can anyone confirm this behavior?
My conclusion above, that even if you don’t download the file, it counts toward the download limit – has anyone else experienced this? (Perhaps I’m missing something)
Assuming this is the case:
2. Is this the intended functionality?
I’m wondering if a dev could comment on this and explain whether there is a purpose to counting API queries toward the limit, even if a download doesn’t occur (and, if you query the download-purchase endpoint, and then actually download the file, would that count as 2 downloads toward the limit)?
3. Is the result from the purchase-download endpoint good indefinitely?
Update: as Gewora pointed out, it is a temporary link. Looking at the URL more closely, this should have been apparent to me
Obviously, I can’t provide this code to my customers if it’s going to burn through their download limit, so I’d like to find out what the best way around this is.
I’m wondering if anyone else has run into this previously and might have some insight. I’m going to submit a support ticket as well (since I need to clear that limit anyway), but I’m hoping others who have played with the API more might have some experience with this.
I don’t think you’re getting spam from that demo site. It sounds more like the spam is coming through a contact form on your site, but because you imported the demo content, the email template in Contact Form 7 still has the text “This e-mail was sent from a contact form on Arista (http://demo.qkthemes.com/arista)" in it.
I’ve invited my buyers for beta testing. I’ve demanded their purchase code to participate.
Exactly, this is how I always do it. I generally just post a topic in my support forum (where everyone is already authenticated anyway) asking for beta testers. I create a new forum section just for feedback on the beta. Tends to work pretty well.
On your downloads page, you should have two options – Installable WordPress file or All Files & Documentation.
You might want to try downloading the other one – it’s possible the author updated one but not the other by mistake. You might be downloading the one that they forgot to update and ended up with an older version.
I can’t believe anyone still falls for that old scam, they’ve been doing it for years.
They tend to prey on the elderly or technologically ignorant who are more likely to believe that “Microsoft” is calling to help them. It’s really sad. Some people are truly pathetic.
If Envato is sending the IRS that we made $50,000, and then our PayPal account says we only received $43,000, that’s a major issue. This would pretty much guarantee that every US author will be audited. Why are we being saddled with this burden when Envato can just pay us a commission as they always have? Keep it simple.
Exactly. We’re going to be audit targets for sure. I have nothing to hide, but it is a process that I will do whatever it takes to avoid, as it is a huge (unnecessary) burden.
Fact of the matter is, we don’t collect this money and we are never paid this money. Envato’s cut is not an expense, and it shouldn’t be treated as income.
Envato, please don’t make honest authors targets for the IRS.