Description
Bug description
Summary
There is no documented or discoverable REST endpoint that returns the
embedded-dashboard UUIDs for dashboards that have “Allow Embedding”
enabled.
The standard list endpoint (/api/v1/dashboard/
) returns dashboard metadata
but omits the UUID required for guest-token generation.
Superset version/environment
- Superset 4.1.2 (Docker image
apache/superset:4.1.2
) - Feature flags in
config.py
FEATURE_FLAGS = { "EMBEDDED_SUPERSET": True, "GUEST_TOKEN": True, }
Steps to reproduce
Enable Allow Embedding on one or more dashboards (UI or PUT request).
Call
bash
Copy
Edit
GET /api/v1/dashboard/?q=(columns:(id,dashboard_title)) or GET /api/v1/dashboard/
Inspect each dashboard object in the JSON response.
Expected result
Each dashboard that is embeddable exposes either
It's an embedded UUID or a link/reference to fetch it.
Actual result
The UUID (or any indication that the dashboard is embeddable) is missing.
Impact
Guest-token flows in client apps (e.g. React with
@superset-ui/embedded-sdk) cannot discover which dashboards can be embedded.
The only workaround is hard-coding UUIDs or querying the metadata DB directly.
Additional context / attempted work-arounds
Tried GET /api/v1/dashboard/ – still no UUID.
Verified that embedded_dashboard rows exist in the metadata DB and contain
the UUID + dashboard_id link.
The deprecated /superset/embedded_dashboard/ endpoint is legacy and
does not list dashboards.
Screenshots/recordings
No response
Superset version
master / latest-dev
Browser
Chrome
Additional context
No response
Checklist
- I have searched Superset docs and Slack and didn't find a solution to my problem.
- I have searched the GitHub issue tracker and didn't find a similar bug report.
- I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.