I was going to use cPanel's API along with enom's to build my own app to handle charges, etc. However, a closer look at WHMCS has revealed that it has it's own API, Now I understand some of the information isn't documented, but it looks dead simple, so I'm not concerned over a lack of examples in some of the calls. What I am concerned about is the overall scope of the API's.
Can I use WHMCS for nothing more than a simpler, unified set of API's with added functionality of handling the storing of product names, prices, addon's, upgrade / downgrades, etc? (unified as in using cPanel and eNom's API's THROUGH WHMCS)
Essentially using WHMCS as nothing more than an API front-end (a front -end to the back end to interface with the actual front end.... haha) to cPanel and eNom. I'd log in to pull reports, add products, adjust prices, etc, but the customers would be on my site which makes API calls to WHMCS.
I need to handle the payments myself, for some other more complicated reasons. So for all the hosting / domain / ssl / web design/ etc i could set it up as recurring, and handle the payments, then tell WHM they've been made so that feature stays active.
But how would an upgrade work? Does WHMCS know if I send a particular customers ID and the upgrade product from what they currently have that it should upgrade the current product? Are there any other issues I could run into beyond this (it's the only one I could think of)?
Hopefully that made sense... - not sure the best way to explain it. If it does, should I be looking to just build it myself or is WHMCS an option for this? Seems like it's really close to what I'm looking for, but upgrades / addons may be an issue....
Question
greatkingrat
I was going to use cPanel's API along with enom's to build my own app to handle charges, etc. However, a closer look at WHMCS has revealed that it has it's own API, Now I understand some of the information isn't documented, but it looks dead simple, so I'm not concerned over a lack of examples in some of the calls. What I am concerned about is the overall scope of the API's.
Can I use WHMCS for nothing more than a simpler, unified set of API's with added functionality of handling the storing of product names, prices, addon's, upgrade / downgrades, etc? (unified as in using cPanel and eNom's API's THROUGH WHMCS)
Essentially using WHMCS as nothing more than an API front-end (a front -end to the back end to interface with the actual front end.... haha) to cPanel and eNom. I'd log in to pull reports, add products, adjust prices, etc, but the customers would be on my site which makes API calls to WHMCS.
I need to handle the payments myself, for some other more complicated reasons. So for all the hosting / domain / ssl / web design/ etc i could set it up as recurring, and handle the payments, then tell WHM they've been made so that feature stays active.
But how would an upgrade work? Does WHMCS know if I send a particular customers ID and the upgrade product from what they currently have that it should upgrade the current product? Are there any other issues I could run into beyond this (it's the only one I could think of)?
Hopefully that made sense... - not sure the best way to explain it. If it does, should I be looking to just build it myself or is WHMCS an option for this? Seems like it's really close to what I'm looking for, but upgrades / addons may be an issue....
Edited by greatkingratLink to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.