-
**Key user needs**
- [ ] Display notification of responses awaiting API retrieval
-
**Key user needs**
- [ ] Display API status
- [ ] Display number of form responses that have reported a problem
- [ ] Resolve the number of problems once the submission is confirmed
-
As part of the Collapsable Panels feature, the API for our new layout engine `kbn grid layout` needs to allow the rendering page to add and remove rows (and delete all the panels within as part of thi…
-
Follow up to #192618
Implement a registry for embeddables to optionally register their configuration schemas for stricter validation and a better API schema definitions for the public Dashboards API.…
-
Follow up to #192618
Register versioned CRUD (Create, Read, Update, Delete) + List public API routes for Dashboards using the v3 content management schema.
API path names, path parameters, and req…
-
We should consider adding link relations in the responses from the Dashboards APIs, i.e. [HATEOAS](https://en.wikipedia.org/wiki/HATEOAS). This is a constraint of the REST specification that makes it …
-
Prior to making the Dashboards Public API available, we should decide on how best to organize the base URL path for the CRUD routes.
Two suggested base paths are
1. `/api/dashboards`
2. `/api/dashboa…
-
If a consumer provides a space id of a Space (either from `/s//api/...` or by specifying the `spaces` array in the request body) to the create dashboard endpoint, we should first determine if a matchi…
-
The dashboard API should return keys in a consistent order.
Ordering is not included in the initial implementation because it used a deep-sort, which may be sensitive to performance issues.
-
It would be great to have the option to revoke or disable an API key directly from the dashboard. This feature would enhance security by allowing users to manage their API keys more effectively, espec…