Skip to content

Manual portals ​

Six services have (as of today) no usable API for customer counts or amounts — their values are maintained manually in Multiverse and from then on participate like any other integration: snapshots, trends, export, billing.

Usage ​

Every manual portal view offers:

  • a table customer → value, directly editable (create, change, delete),
  • the usual snapshot mechanism: the nightly run freezes the maintained values daily — changes take effect from the day of the change, the history stays correct.

The values are typed as text and read strictly: a decimal comma or point, grouping ("1.234,56") and a trailing € sign are fine; an empty value, something that is no number, an entry that could be thousands or decimals ("1.200"), a value without a customer and a customer entered twice are marked in the dialog and nothing is saved until they are fixed — an unreadable amount is never saved as 0. When the last entry of a portal is deleted, the next snapshot records the portal as empty and the entry is gone from billing.

Values only need to be touched when they change

A maintained value stays in effect until it is changed — the snapshot handles the daily carry-forward automatically.

The portals in detail ​

PortalMaintained valueWhy manual?
ExclaimerLicenses per customerThe partner/cloud API requires an MSP token issued by Exclaimer (requested); after that, switching to the API is planned
GoogleAmount (€) per customerAmounts depend on the purchasing channel (direct partner vs. distributor); an API switch is being evaluated
konsoleHHostings (count) per customerManaged hosting without a partner API; the price comes from the weclapp article mapping, only the quantity is maintained
NetwrixLicenses per customer1Secure (MSP platform) has no public API yet — only a feature request in the Netwrix forum
RenderAmount (€) per customerThe Render API offers no invoice/cost endpoints
SoSafeUsers per customerno API access for partner license counts

Billing ​

Amounts (€) are typically billed in weclapp as a line item with quantity × 1 and the amount as a price override; unit counts (licenses, users) like any other metric via the article mapping.