Signed embedded Cloud
Place Apification inside the customer portal through a short-lived signed iframe session.
Commercial model
Reseller integration
Embed Apification through Cloud iframe, API, inherited configuration and visual themes.
Overview
Embed Apification through Cloud iframe, API, inherited configuration and visual themes.
Features
What Reseller integration can do
API provisioning
Create customer accounts, users and initial configuration from the reseller application.
Inherited visual identity
Apply effective themes and account defaults so the embedded experience fits the reseller product.
Effective permissions and quotas
Resolve master policies and customer settings before exposing services or accepting new consumption.
Host-to-iframe communication
Coordinate selection, completion and navigation events with validated browser messages.
Isolated customer context
Keep every signed session limited to the intended subaccount, user and permitted resources.
Operational traceability
Monitor provisioning, access, usage and integration failures from the responsible account context.
Embedded session
Build customer context before rendering the iframe
Identity, effective policy and visual configuration are resolved server-side for every launch.
-
01 Resolve customer
Identify the subaccount, user, permitted services and current limits.
-
02 Request a signed session
Create short-lived launch data from the trusted reseller backend.
-
03 Embed and coordinate
Render Cloud and exchange only validated host and iframe events.
-
04 Observe the result
Track provisioning, access, usage and failures in the correct account context.
Operational detail
How Reseller integration works in practice
Reseller integration combines backend provisioning with a signed embedded Cloud, allowing customers to work inside the reseller product while account boundaries remain enforced by Apification.
Backend and browser have different roles
Provisioning, secrets and session signing stay on trusted servers; the browser receives only the short-lived context required to render the embedded experience.
Provisioning needs a stable contract
External customer identifiers should map predictably to Apification accounts and users so retries do not create duplicate or disconnected resources.
Effective configuration is resolved at launch
Master policies, customer overrides, theme and permissions combine into the experience shown for that specific signed session.
Observability completes the integration
Provisioning responses, iframe events, API errors and consumption records provide the evidence needed to support a customer without guessing.
Frequently asked questions
Questions about Reseller integration
No. The reseller backend should authenticate the customer and request or generate the signed short-lived context without exposing reusable secrets.
A session should be scoped to one intended customer context. Switching customers requires a newly authorised and signed context.
Yes. Effective themes and supported appearance settings can adapt the embedded experience while preserving functional and security boundaries.
Customer, user and initial-configuration creation should use stable external identifiers or idempotency controls so safe retries do not create duplicates.