This is so annoying!
Why have you remove the code
property of /authors/sales
endpoint?
How we supposed to setup a support system when you constantly change something on your API?
This is so annoying!
Why have you remove the code
property of /authors/sales
endpoint?
How we supposed to setup a support system when you constantly change something on your API?
Just curious, What the code
thing supposed to do?
And what kind of support system are you building. means every author now needs one
I contains the purchasecode of the sale
Oh no itās gone has it?
edit: ahh crap. well that was fun while it lasted. haha
itās still in /buyer/purchases so we can at least still verify individually that way.
I can see why it was removed from /author/sales - that would have let us get the username (and user details) of every single sale in history, something that isnāt currently possible (and probably shouldnāt be possible) through the normal market sites.
Putting my vote in for a āsupported_untilā flag in /search/comments endpoint.
No, this should be possible!
Iām the seller. I have the right to get the data. When Envato was the seller I had no problem when this data is private