Please Provide API to protect our Scripts

That's will be good for All of Us We can Give Online support and ticket support too

and also make website where user register and we will give them support

API will help to Valid Purchase code Instantly So we don.t need to verify manualy

It's been 10 months ago we need purchase code but now it's 2020 we did not get this why Admin please add Purchase or API

Any updates on this?

Frederick, Staff Jun 22, 2019
We will be adding a license check tool for authors to check if the user should receive support.


You are replyed. Where are license check tool ? Give me link.

any update for this?

We have a license manager of our own, but we need some api from codester to automate purchases of all codester buyers and activate the product.
Since we sell on Envato too, the envato api helps the buyers to activate the product on their own without any human interference. While, codester buyers are forced to fill a form, attach the license certificate and purchase date, and we should check in the dashboard if the purchase is valid and then add their data to our licensing db. This process is hectic and most buyers can't use the script instantly after purchase.

We currently have a license check in the author dashboard to see if somebody did indeed purchase your items before giving support. Currently because of to many issues with encrypted code and license checks we do not support license checks and encrypted code.

License checks will never be without sacrifices for the buyer. Buyers expect to buy an open source product and and often very disappointed to get encrypted code. One of the key idea's of Codester marketplace is that all items have a fully readable source code that be modified as you want.

Also buyers expect to be able to purchase items without any friction. Having to register somewhere else after each item that is purchased and having to share their contact details with each author is something we are against.

The idea of your work being distributed illegally is very scary. Other then that, even taking out of the equation that these scripts also receive lower review scores and end up with less sales as well, our experience is that the losses made by refunds because of encrypted code and license systems that have issues are many times more then the hand of full cases (of tens of thousands of sales) where a purchased script got distributed illegally.

Our experience is that such systems do not belong on a marketplace.
It is understandable somebody can't get rid of the worry that somebody can steal their work and have you no control on distribution. For us the sacrifices a marketplace has to make to facilitate this are simply to impactful.

Yes, i have seen the license checker in the author dashboard, but since we have our own support ticket system, we would like an api which can make the process seamless.

Also, i have not mentioned that scripts need to be encrypted. We don't sell encrypted scripts. We just want to improve the experience for the actual buyers.

License check would've been very easy if there was an api. I know it's gonna get nulled anyways but we'll handle that part as long you provide some api. ( Even if it's the same license code checker in the dashboard in the form of api )

I hope you can understand us.

I think the tenets of success in business is to pay attention to your customers and know what they actually need from you and not necessarily what you are offering to them.

I believe if a poll should be conducted amongst the authors on this platform on whether Codester should implement an automated license key validation API (like is applicable on Envato) or not, those in support for it will win hands down.

License key validation does not stop code piracy completely (in fact, no system can guarantee that) but it will mitigate it to a good extent. Only buyers who are knowledgeable enough (less than 20%) can be able to mess around the code to bypass the script installation license key validation. The rest will have no option than to respect the license key validation process to be able to install the script.

If the license validation process does not offer any benefits to authors and marketplace (more sales for additional licenses), Envato would have scrapped it a long time ago.

What we have now on Codester is that a buyer can comfortably install a purchased script (with Regular license) on multiple domains without any restriction whatsoever. But with license key validation, this will not readily be possible because a license key will be tied to the domain that first used it (though, this can be changed by the author system in rare cases of domain migration). Any other domain requesting license key validation with same key will be denied, unless in the case of Extended license key that can be installed on multiple domains.

The benefits of license key validation API cannot be over emphasized. This will definitely bring in more sales (additional license key purchase) to the benefit of both authors and Codester. The confidence of authors will also be boosted and more reluctant authors with quality items will now embrace Codester knowing that their hard work are protected from usage abuse.

And to implement the license key validation API is not difficult since you already have purchase license key in place. The only thing remaining is to provide authors an API key and endpoint which they can call during installation to verify if the supplied license key belongs to their listed item on Codester.

If you guys are afraid that some authors may not implement it correctly, then you can test it out during your script review process. A simply tutorial on how to implement it can also be made available to authors who wish to implement it.

I believe if this is implemented, many authors will embrace it and both parties (authors and Codester) will be happy at the end of the day.

The way I see things, Codester is just an interface where we can sell our projects. I don't think it's Codester's job to protect our work, because we should do it ourselves. For example, I introduced a license verification API in each application only for updates and not for installation.

The verification is done through a site that I own and where I have control over all the applications. If the client buys my PRO license, then they can update the application, if not, they can use it without any worries. My opinion is that everyone should protect their application as they know best, and if someone "borrows" my project, it should be good for them. After all, we have to give away freebies sometimes, and the world is quite vast and has room for everyone, and they would only advertise me and that way I become even more famous.

Why do I say this, because a friend gave me a copy of the Perfex application purchased from Envato, to help him improve it, but I can use it for myself if I want (of course, I don't want to). The application only has a verification license for updates, so not for installation or use. Now, do you think the people at Perfex didn't think that someone could take their project for free and use it? Yes, but they still didn't code it. Why, because as Frederick said, that would make customers unhappy.