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.
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
| Portal | Maintained value | Why manual? |
|---|---|---|
| Exclaimer | Licenses per customer | The partner/cloud API requires an MSP token issued by Exclaimer (requested); after that, switching to the API is planned |
| Amount (€) per customer | Amounts depend on the purchasing channel (direct partner vs. distributor); an API switch is being evaluated | |
| konsoleH | Hostings (count) per customer | Managed hosting without a partner API; the price comes from the weclapp article mapping, only the quantity is maintained |
| Netwrix | Licenses per customer | 1Secure (MSP platform) has no public API yet — only a feature request in the Netwrix forum |
| Render | Amount (€) per customer | The Render API offers no invoice/cost endpoints |
| SoSafe | Users per customer | no 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.