Master account hierarchy
Operate customer subaccounts from one reseller-owned structure while keeping their resources and activity separated.
Commercial model
Apification for resellers
Group customer subaccounts under a master account and control services, permissions, quotas and consolidated usage.
Overview
Group customer subaccounts under a master account and control services, permissions, quotas and consolidated usage.
Features
What Apification for resellers can do
Customer provisioning
Create users and subaccounts with the initial services, roles and defaults required by each commercial package.
Service and permission policies
Control which capabilities, extensions and account actions are available to each customer.
Quotas and consolidated usage
Assign storage and consumption limits per subaccount and review totals from the master account.
Customer-context operation
Enter the appropriate account context for support and administration without mixing customer ownership.
Independent pricing and billing
Keep end-customer contracts, final prices and invoicing under the reseller commercial model.
API-ready administration
Automate repeatable provisioning and configuration tasks from the reseller backend.
Customer lifecycle
Operate every customer from one governed structure
Provisioning, policy, support and usage stay connected without mixing customer resources.
-
01 Design the offer
Define included services, roles, limits, branding and external price.
-
02 Provision the customer
Create the subaccount, users and initial configuration.
-
03 Govern operation
Apply permissions and quotas and monitor consolidated consumption.
-
04 Support and expand
Work in the right customer context and evolve the offer as needs change.
Operational detail
How Apification for resellers works in practice
The reseller model separates commercial ownership from platform operation: the reseller manages the customer relationship while Apification supplies governed accounts, services and consumption controls.
Hierarchy without shared ownership
The master account provides administration and consolidated visibility while each subaccount retains its own users, Cloud resources, projects and activity.
Policies become part of the product
Available services, extensions, roles, themes and account defaults can reflect the package sold to each customer instead of relying on manual setup.
Usage is visible before billing
Per-customer quotas and consolidated totals give the reseller operational evidence while final pricing, invoicing and collection remain external responsibilities.
Support uses explicit customer context
Administration and assistance should identify the active subaccount clearly so actions, resources and audit context remain attributable to the correct customer.
Frequently asked questions
Questions about Apification for resellers
They remain associated with that customer account. Master-account administration does not merge resources from different customers.
The reseller keeps control of end-customer contracts, pricing and invoicing unless a separate commercial agreement states otherwise.
Yes. Service availability, roles, extensions, storage and consumption policies can be adapted per subaccount.
Support should use the explicit customer context and authorised administration flow so every action remains separated and traceable.