ZenotiHelp

Marketplace Embed — Auth-Recovery Token Endpoint

ZTZenoti Docs Team Updated October 27, 2026 3 min readGuide

The Zenoti Marketplace storefront runs inside an embedded frame within the Zenoti web application. Occasionally, the authentication token the frame received at load time can expire or be lost mid-session. When that happens, the host Zenoti page silently issues a fresh token and returns it to the frame, restoring your session without interrupting your work. This article explains what that process does, when it applies, and what you can expect if conditions are not met.

Audience: Zenoti administrators and technical staff who manage or monitor the Zenoti Marketplace experience within their organization's Zenoti deployment.

Before you begin

  • Your organization must have the Zenoti Marketplace enabled. If the Marketplace is not enabled for your deployment, the recovery mechanism is not active and you will not see the Marketplace in your Zenoti menu.
  • You must be signed in to Zenoti with an active session. An expired parent session cannot produce a recovery token.

Permission: You need the role permission that allows your role to view the Marketplace menu entry. Your administrator controls whether your role can see the Marketplace. For more information, see the admin articles.

Steps

How the auth-recovery process works

The auth-recovery process runs automatically in the background. There are no manual steps you need to take — the process is invisible when it succeeds. Understanding the steps below helps you interpret what you see if the process does not complete successfully.

  1. While you are browsing Zenoti Marketplace inside Zenoti, the embedded storefront detects that its authentication token is no longer valid.

  2. The storefront signals the host Zenoti page that a new token is needed.

  3. The host Zenoti page checks whether the Marketplace is enabled for your deployment.

    • If the Marketplace is not enabled, the request is rejected. No token is returned, and you will see an error state within the storefront frame. Contact your administrator to confirm whether the Marketplace is active for your organization.
  4. The host page checks whether your Zenoti session is still active.

    • If your session has expired, you are redirected to the Zenoti sign-out flow rather than receiving a new token. Sign back in to Zenoti and then navigate to the Marketplace again.
  5. If both checks pass, the host page mints a fresh token server-side and returns it to the storefront frame. Your browsing session continues without a visible sign-in prompt or page reload.

What the re-minted token carries

The fresh token carries exactly the same identity and context as the token issued when the host page first loaded:

  • Your Zenoti user identity
  • The center context active in your session
  • Your session type, including support-login sessions if that applies to your account

No change in permissions or access level is possible through the recovery path. The re-minted token does not grant broader access than the original.

Note: If you are operating within a support-login session, the re-minted token preserves that session type. Your support context is not lost during a token recovery.

Tips

  • If the storefront frame shows an error or signs you out unexpectedly, check that your main Zenoti session is still active. Refreshing the parent Zenoti page signs you back in through the normal flow.
  • If your organization recently changed Marketplace enablement settings and you encounter persistent token-recovery failures, ask your administrator to confirm the Marketplace is fully enabled before troubleshooting further.
  • Token recovery is silent by design. If you notice a brief loading state in the Marketplace frame and then your session continues normally, that is the recovery process completing successfully.
  • If you are signed in through a support-login session and the Marketplace frame drops its token, the recovery process preserves your support context — you do not need to re-establish the support session.

Troubleshooting

Symptom Likely cause Resolution
The Marketplace frame shows a sign-in screen or error state instead of restoring your session automatically Your Zenoti parent session has expired Sign back in to Zenoti, then return to the Marketplace. The recovery process requires an active parent session.
Navigating to the Marketplace returns a "page not found" or unavailable state The Marketplace is not enabled for your organization's deployment Contact your administrator or Zenoti to confirm whether the Marketplace is active. Until it is enabled, no token recovery is possible and the Marketplace entry will not appear in your menu.
The storefront frame reloads with a full sign-in prompt each time you return to the Marketplace The parent session expires quickly due to session timeout settings Check your organization's session timeout configuration. If timeouts are expected, the normal sign-in flow applies when the parent session ends.
Was this article helpful?
Your feedback helps us improve our documentation.