{"ok": true, "database": "docs", "table": "sections", "rows": [{"id": "changelog:extra-support-for-row-and-query-pages", "page": "changelog", "ref": "extra-support-for-row-and-query-pages", "title": null, "content": "Row and query JSON pages now support the same  ?_extra=  mechanism as table pages. Row pages can request extras such as  foreign_key_tables ,  query ,  metadata  and  database_color ; arbitrary SQL and stored query pages can request extras such as  columns ,  query ,  metadata  and  private . The implementation was refactored into a registry of extra classes shared by all three page types. \n                 New generated reference documentation describes every  ?_extra=  parameter available on table, row and query JSON pages, with example output captured from a live Datasette instance at documentation build time. See  Expanding JSON responses  for the full list. \n                 You can explore the new extras using this  Datasette extras API explorer tool . \n                 Other improvements and fixes to the extras mechanism: \n                 \n                     \n                         Extras that exist to serve the HTML interface ( filters ,  actions ,  display_rows ) are no longer advertised or reachable through the JSON API, where requesting them previously returned a 500 serialization error. \n                     \n                     \n                         The pre-1.0  ?_extras=  (plural) parameter on row pages has been removed - use  ?_extra=foreign_key_tables  instead.", "breadcrumbs": "[\"Changelog\", \"1.0a33 (2026-06-11)\"]", "references": "[{\"href\": \"https://tools.simonwillison.net/datasette-extras-explorer\", \"label\": \"Datasette extras API explorer tool\"}]"}], "primary_keys": ["id"], "primary_key_values": ["changelog:extra-support-for-row-and-query-pages"], "query_ms": 4.112582999368897, "truncated": false}