errors.databases.listList the connected databases and the suggested ones (databases the project’s connected apps use)
Request syntax
GET /errors/api/projects/{id}/databasesPath parameters
idRequiredstring
Constraints: uuid
Response
200 with { databases, suggestions }: `databases` the connected ones by name, each with dbInstanceId, identifier (null unless you have rds:DescribeDBQueryInsights or rds:DescribeDBInstances on it), status, readable (you may read its statements) and createdAt; `suggestions` the PostgreSQL databases the project’s connected apps use (DATABASE_URL) that are neither connected nor dismissed, each with appId, appName, dbInstanceId, identifier and roleName (the app’s own role, null for the master user), listed only when you have errors:UpdateProject on the project and rds:DescribeDBQueryInsights on the database, else empty. 404 when the project does not exist, 403 without errors:ListProjects on it.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow errors:ListProjects on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud errors databases list idcurl -X GET "https://console.platform.deutschecloud.app/errors/api/projects/id/databases" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_databases_list.