Unlisted public app used across multiple client accounts — connection caps, rate-limit scope, and removing the consent-screen warning?

API & SDK
1

Hi team,

I’m a registered Development Partner running a public app (OAuth 2.0, type
External Integration) that I keep unlisted — clients connect via the
standard OAuth flow rather than through the Add-on Store. It’s live against one
production account and working well. Before connecting further client accounts
I’d like to confirm four things so I build this correctly:

  1. Connection cap — is there any limit on how many separate ServiceM8
    accounts an unlisted public app can be authorised against at once? Does a
    Store listing change that?
  2. Rate-limit scope — the docs state 180 requests/min and 20,000/day. Can
    you confirm these apply per connected account, rather than as one global
    quota shared across all accounts the app connects to?
  3. Commercial use while unlisted — is operating a single unlisted public
    app as a paid, managed service across multiple clients’ accounts (each
    granting their own OAuth consent) within the Partner Agreement? If this is
    better handled off-forum, who’s the right contact to confirm it formally?
  4. Consent-screen warning — the OAuth consent screen for an unreviewed app
    warns users the app is unofficial and to proceed only if they trust the
    developer. Is there a path to have an app reviewed/approved so the warning
    is removed without publicly listing it on the Add-on Store? My onboarding
    is deliberately high-touch (I connect each client personally) — I’m not
    after self-serve installs, just a consent screen that doesn’t undermine
    client trust.

I can share my App ID privately if useful. Thanks!

Brad — AppMate Consulting