Running WHMCS alongside a no-code mobile app build?

[Nathan Davis]

I'm setting up a small hosting business and picked WHMCS as the billing side, mainly because I want client accounts and invoices handled in one place. Separately, I've been looking at no-code and AI mobile app builders for a customer-facing app, since I don't have a development background. The thing I keep going back and forth on is how the two would actually fit together. I understand WHMCS has an API, but I'm unsure whether a builder-generated app can call it reliably for things like checking account status or submitting a support ticket, or whether that requires custom work beyond what a no-code tool offers. I'm also wary of picking a builder now and finding it can't handle authentication or payments later. Has anyone connected a WHMCS install to an app built on one of these platforms, and what should I check before committing to one?

[Waqas Ahmed Waseer]

It works, but not with the app talking to WHMCS directly. Plan on a small backend in the middle, even if everything else is no-code.

The WHMCS API authenticates with admin-level API credentials. Those can act on any client account, so they must never ship inside a mobile app, where anyone can extract them. A lot of no-code builders will happily let you paste credentials into an API connector, and that's the trap to avoid. Have the app call your own small service (a serverless function, or a little PHP or Node endpoint), keep the API credentials only there, and lock them to that server's IP with the API IP restriction setting.

For login, WHMCS can act as an OpenID Connect provider (Configuration > System Settings > OpenID Connect). If the builder supports a generic OAuth2/OIDC login, clients sign in with their existing WHMCS account, and your backend maps the verified login to their client ID. That way a client can only ever see their own services and tickets, because the backend takes the client ID from the login, never from whatever the app sends.

For the features you mentioned, the backend calls GetClientsProducts for account and service status, GetInvoices for billing, and OpenTicket / GetTickets for support.

For payments I wouldn't build checkout into the app at all. Have the backend call CreateSsoToken and open the invoice or billing page of the WHMCS client area in a browser view. The tokens are single-use and valid for at most 60 seconds, so generate one when the user taps, not in advance. Your existing gateway, 3D Secure and fraud checks keep working, and you don't drag card handling into the app.

Before committing to a builder, I'd check four things:

1. Custom OAuth2/OIDC login, not only its own user system or social logins.
2. Calling your own REST endpoints with a bearer token in the header.
3. Opening a URL in an in-app or external browser.
4. Whether you can host or export the backend logic yourself.

If it fails the first two, it will fight you later.

Honestly, for a new hosting business I'd start with a mobile-friendly client area theme and add a native app once clients actually ask for one. Most of what they need day to day (pay an invoice, open a ticket, check a service) already works in the client area on a phone.