Repository navigation
REST API Exports doen not work (dashboard, dataset etc) #28180
Description
Bug description
Any API endpoint for exporting data returns the same error:
"message": "Not a valid rison schema {} is not of type 'array'\n\nFailed validating 'type' in schema:\n {'items': {'type': 'integer'}, 'type': 'array'}\n\nOn instance:\n {}
This happens on 3.1.1, 3.1.2 and 4.0.0 using superset official docker container.
How to reproduce the bug
- in your browser, goto swagger/v1
- Authenticate with tokens
- Klick on any GET endpoint example: api/dataset/export
- klick try it out
- klick execute
Screenshots/recordings
Superset version
3.1.2
Python version
3.10
Node version
16
Browser
Chrome
Additional context
Database used is Postgres 16
LDAP used for authentication (Active Directory)
FEATURE_FLAGS = {"TAGGING_SYSTEM": True, "RLS_IN_SQLLAB": True, "DRILL_TO_DETAIL": True, "ALERT_REPORTS": True, "DASHBOARD_CROSS_FILTERS": True, "DASHBOARD_RBAC": True, "THUMBNAILS" : True, "THUMBNAILS_SQLA_LISTENERS": True, "ENABLE_TEMPLATE_PROCESSING": True, "ENABLE_TEMPLATE_REMOVE_FILTERS": True, "ENABLE_SCHEDULED_EMAIL_REPORTS": True, "EMAIL_NOTIFICATIONS": True,"EMBEDDED_SUPERSET": True}
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.
Activity
FiiL123 commentedon Sep 17, 2024
This is not working for us either in 4.0.2.
@michael-s-molina; @rusackas can someone please check.
rusackas commentedon Apr 11, 2025
Maybe @dosu-bot can help, but I haven't a chance to try to reproduce this, and it's been silent for quite a while. I assume this is still an issue?
msyavuz commentedon Jul 17, 2025
I can confirm it still exists. In web-app we put a token in the query parameters along with the dashboard id's. This is probably an issue with how swagger is setup for these endpoints
rusackas commentedon Mar 11, 2026
Confirmed still present in master per @msyavuz — the issue is related to how the Swagger UI sets up these export endpoints (token in query params). A fix may require updating the Swagger spec or endpoint authorization for the export endpoints. PRs welcome.
rusackas commentedon Jul 21, 2026
This isn't the export endpoint being broken, rather it's that
get_export_ids_schemahas no example, so Swagger UI's "Try it out" defaultsqto{}instead of an array like!(1,2,3). Adding an example to the schema would fix the confusion.Abdulrehman-PIAIC80387 commentedon Jul 21, 2026
Thanks @rusackas — picking this up. Adding
"example": [1, 2, 3]to all 6get_export_ids_schemadicts (dashboards, charts, datasets, databases, saved_queries, themes) so Swagger UI's "Try it out" pre-fills a valid array. PR incoming.rusackas commentedon Jul 22, 2026
Thanks for picking this up @Abdulrehman-PIAIC80387, #42265 adds examples to the six
get_export_ids_schemaschemas so Swagger's Try it out pre-fills a valid array instead of{}. That should close this out once it lands.fix(api): add example to export/delete/fav_star ids schemas so Swagge…
fix(api): add example to export/delete/fav_star ids schemas so Swagge…