Paddle looks really nice actually; switching providers probably won't help with the motivation factor, and it looks like they don't provide HTTP API SDKs (that's a lot of acronyms, sorry) in any language, so it would be a bit more work to use, not to mention that it's a lot more expensive, but I wonder if it's worth it either way? You've got me curious, I'll have to look into it a bit. Thanks.
eww, that being said, their API appears to use exclusively POST requests for everything (even things where you're getting something) and puts auth in the body. I guess it's no big deal, but I'm not sure how I feel about that. It's harder with my HTTP library because I can't abstract away the post parameters as easily as I can headers (without doing unnecessary decoding then re-encoding them), but that's arguably a problem with my HTTP library, not Paddle. Still, feels different to everything else, which is odd.
Upon further investigation, nothing about their API is consistent or well done (and/or the docs are terrible and incomplete). I understand that this is a small company, but this level of inattention to detail is unacceptable. What are they doing with my customers financial data if they can't even get a simple API right? Even if I did decide to use them, the docs are so incomplete I'm not sure that I could actually build an integration without reverse engineering what half these values can be, or guessing at parameters that are used in examples but left out of the actual list (where a list even exists), etc.
