WHO IT’S FOR
For platforms that resell learning delivery.
If you sell training software to many organizations, you need each customer’s content and learners kept separate, with usage you can meter and bill. The Customer API gives you that multi-tenant control plane: spin up a workspace per customer, set its limits, brand it, and see the whole portfolio from one parent account.
- EdTech platforms & LMS vendors
- Training resellers & agencies
- Enterprises with many business units
What you control
A control plane for many customers.
Child workspace provisioning
Create, configure, and retire tenant workspaces via the API — each with its own packages, dispatches, and keys. Suspend and reactivate a child without touching the parent.
Hard tenant isolation
Data and credentials never cross tenant boundaries — isolation is enforced at the platform, not by convention. A parent can never reach another parent’s children.
Per-tenant quotas
Set active-learner, package and storage limits per tenant. New learners and packages past a child’s quota are refused, and alerts fire at 80% and 100% before they bite.
Rolled-up billing
Usage aggregates to the parent for a single invoice, while you meter and price each tenant however you like.
Branding & custom domains
Custom domain and branded player per tenant, so each customer sees their product, not yours. On Scale and Enterprise, full white-label: the learner-facing player shows the course title, never Allure Connect.
Admin APIs and spend caps
Programmatic membership, posture, and billing-metadata review across every tenant from the parent, plus a spend cap per child workspace and per API key.
WORKS WITH ALLURE LMS
The Connect workspace behind an Allure LMS academy.
Allure LMS academies deliver their SCORM courses through Connect. Each LMS-managed workspace uploads and delivers SCORM through Connect with an LMS service token that can only act inside LMS-managed workspaces, never in yours or any other customer’s. The LMS bills its own academies, so LMS-managed workspaces are not counted against a Connect plan: no Connect learner cap, overage or storage quota applies to them. Plan features still follow the plan.
- Allure LMSAvailable
LMS-managed workspaces
An academy on Allure LMS gets its own Connect workspace for SCORM hosting and launch tracking. Pricing for the academy is the LMS plan, for example LMS Growth.
- Allure Training OSComing soon
Connect learners in Training OS Team
Training OS Team includes 250 Connect learners in a per-customer Connect workspace, provisioned through this Customer API.
- Your platform
The same API for you
Everything the family products use is the Customer API on this page: parent-scoped keys, per-child quotas and rolled-up billing, from Growth up.
FOR THE TECHNICAL BUYER
One parent key, many isolated tenants.
A parent credential provisions child workspaces, each with scoped keys and enforced quotas. Tenant isolation is a platform guarantee; usage and audit events are attributed per tenant and aggregated to the parent for billing and posture review. Mint the parent key in Integrations → API keys with Customer API access (Growth and up; a live key on a top-level workspace). The child’s own API key is returned once, on create.
- Parent / child workspace model with scoped keys
- Platform-enforced tenant data & access isolation
- Per-tenant quota enforcement + usage attribution
- Admin APIs for membership, posture & billing metadata
- Growth and up; Scale and Enterprise: the full Customer API with unlimited child workspaces
POST /api/v1/customers
Authorization: Bearer ac_live_… # parent-scoped key
{ "name": "Globex Training",
"quotas": { "active_learners": 5000,
"packages": 50, "storage_gb": 25 } }
← 201 · workspace created
# child workspace id + child API key (ac_live_…, shown once)
PATCH /api/v1/customers/{id}/quotas
PUT /api/v1/customers/{id}/domain
GET /api/v1/customers/usageStatus, limits and plans
- Status
- Available
- Plans
- Growth, Scale and Enterprise include the Customer API and child workspaces. Scale and Enterprise add the full Customer API (unlimited child workspaces) and full white-label. See plans
- Limits
- Parent-scoped API key with Customer API access (live key, top-level workspace)
- Per-child quotas: active learners, packages, storage
- Rolled-up billing: children’s active learners count on the parent invoice
- Custom domain and branded player per child; spend cap per child and per key
- Docs
- Build a learning app on Connect
Questions about Multi-tenant / Customer API
What is a child workspace?
How is tenant data isolated?
Which plan unlocks it?
How do I authenticate?
POST /api/v1/customers creates a child (with optional quotas) and returns the child’s own key once. Owners and admins can also manage children from the dashboard.How does billing work for children?
Does Allure LMS use this?
PAIRS WITH
Works with
- Available
Developer API
The REST surface, keys, and webhooks behind every tenant.
- Available
SCORM Dispatch
Give every customer workspace its own dispatches and controls.
- Available
Rustici Engine comparison
Compare child-workspace provisioning in a hosted backend with an embedded or managed standards engine.