My goal
I want to embed a few pages of one of our Retool apps into our own customer-facing web app. The people using it are external customers who don't have Retool accounts, and they shouldn't hit a Retool login. The app was built with the new app builder (app_type: react), served at /rr/app/, and it's multipage via React Router.
Issue:
I can't find a way to generate a pre-authenticated, single-use embed URL for a new app builder app the way POST /api/embed-url/external-user works for classic apps. The classic endpoint authenticates fine, but the URL it returns lands on the classic /embedded/authed/ route, which just shows an empty shell for our React app.
The /rr route always asks a logged-out user to sign in. Every embed and external-user doc I've read is labeled classic apps only, and I couldn't find a new-builder equivalent.
Steps I've taken to troubleshoot:
- Added our parent origin to frame-ancestors under Settings, App Security. After that, a plain renders correctly for a user who is already logged into Retool.
- Called POST
/api/embed-url/external-user with landingPageUuid set to the app UUID. It returns 200 and a single-use URL, but opening it lands on /embedded/authed/ and shows an empty shell for the React app.
- Set the embed-redirect destination to
/rr/app// and opened it in an Incognito window (logged out, like a real customer). It bounced to the Retool login. A plain /rr iframe in Incognito does the same.
- Read the embed and external-user docs and several community threads. All of it is scoped to classic apps, and I found nothing covering external embedding for the new builder.
Additional info: (Cloud or Self-hosted, Screenshots)
- Retool Cloud, with a custom domain configured (retool..com).
- App type: new app builder (React), multipage via React Router.
Summary
Wants to generate a pre-authenticated, single-use embed URL for a new app builder (React, /rr/app/) app so external users without Retool accounts can access embedded pages, but the classic POST /api/embed-url/external-user flow only lands on the classic /embedded/authed/ route (empty shell for React apps) and the /rr route always forces a login.
AI Response
This is a current limitation rather than a misconfiguration: the new app builder is still in beta, and public/external access — including pre-authenticated embed URLs and public/embedded link generation — is not yet supported for new-builder (React) apps. Retool staff have confirmed this directly and noted these capabilities are actively being worked on, while all embed and external-user tooling (including POST /api/embed-url/external-user) remains scoped to classic apps. For now, the only supported paths are to keep external-facing embeds on a classic app or to have users authenticate with a Retool session; there is no new-builder equivalent of the external-user embed endpoint yet. Following the linked threads is the best way to track when this ships.
Sources
Unable to Generate Public/Embedded Link for New App
Retool staff confirm that public/embedded link generation is not yet available in the new app builder beta and is actively being added, pointing to the tracking thread for updates.
Does React app builder have any fully-public no-account mode?
A Retool staff reply directly states that public (no-account) access is not yet supported in the new app builder, corroborating why logged-out external users are bounced to login.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 
Hi! This is currently a feature we are building out, and we hope to have a beta version next week! I can turn the feature on for you when it’s available on cloud if you’d like. If so, do you have an email that would be best for me to reach you at?
1 Like
Hi Isabella,
Thank you. It is budi.irawan@producepay.com
@Isabella_Borkovic we’re looking forward to receiving beta version this week. This is currently blocking our work as we had assumed the New App would include the same the pre-authenticated URL feature as the Classic App.
Hi Isabella,
We have a very similar use case and would also be interested in having this beta enabled for our Retool Cloud workspace when available.
We're using the New App Builder and need users to access the application without first authenticating with a separate Retool account. Our authentication is handled through Microsoft Entra ID / Microsoft 365.
Our Retool workspace is allamericangrub and the application is Food Truck Operations Manager.
I'd be happy to provide my email is ehess@allamericangrub.com. Could our workspace also be added to the beta?
I can! One caveat is that we haven’t configured embedded apps for orgs with custom domains yet, but it seems like you guys don’t have that feature!