Endpoints

REST API: Deletes the database with the given ID.

REST API: Returns the database with the given ID.

REST API: Returns all databases the token has access to. Optionally filter by project ID.

REST API: Returns databases for the given project.

REST API: Updates the database with the given ID. logicalId cannot be combined with branchId or branchGitName in one request; move the database first, then set its logicalId.

REST API: Destructive operation — this immediately and irreversibly overwrites all data in the target database with the contents of the specified backup. Any data written since the backup was taken will be lost. Ensure you have a recent backup of the target database before proceeding. Replaces the data in an existing database from a backup. Connections and credentials are preserved — only the data layer is replaced.

REST API: Creates a new database in the specified project. logicalId cannot be combined with branchGitName; pass branchId instead.

REST API: Creates a new database for the given project.

REST API: Returns backups for the specified database.

REST API: Returns usage metrics for the specified database.

REST API: Returns all connections for the given database.

REST API: Creates a new connection string for the given database.

REST API: Revokes the integration tokens by integration ID.

REST API: Revokes the integration tokens with the given client ID.

REST API: Returns a single integration by its ID.

REST API: Returns integrations filtered by workspace ID.

REST API: Returns integrations for the given workspace.

REST API: Deletes the project with the given ID.

REST API: Returns the project with the given ID.

REST API: Returns the list of projects the token has access to.

REST API: Updates the project with the given ID.

REST API: Transfer the project with the given ID to the new owner's workspace

REST API: Creates a new project with a postgres database.

REST API: Returns subscription information for the workspace with the given ID.

REST API: Returns the workspace with the given ID.

REST API: Returns the list of workspaces the current token can access.

REST API: Deletes the connection with the given ID.

REST API: Returns the connection with the given ID.

REST API: Returns all connections the actor has access to, with optional database filter.

REST API: Generates new credentials for the connection with the given ID. Revocation of the previous credentials is best-effort.

REST API: Creates a new connection for the specified database.

REST API: Returns all available regions across products. Optionally filter by product.

REST API: Returns the user, workspace, and credential represented by the current token.

REST API: Returns all available regions for Prisma Accelerate.

REST API: Returns all available regions for Prisma Postgres.

REST API: Revokes and deletes the bucket key with the given ID.

REST API: Permanently deletes the bucket with the given ID, all objects stored in it, and all its access keys. This action cannot be undone.

REST API: Returns all access keys for the given bucket.

REST API: Returns the bucket with the given ID.

REST API: Returns all object-store buckets the token has access to. Optionally filter by project ID.

REST API: Updates the display name, logical id, or branch of the bucket with the given ID. The display name is a label only: the provider bucket name, the objects, and the access keys do not change. logicalId cannot be combined with branchId or branchGitName in one request; move the bucket first, then set its logicalId.

REST API: Creates a new access key for the given bucket. The secretAccessKey field is returned exactly once in this response and is never stored — copy it immediately.

REST API: Creates a new object-store bucket in the specified project.

REST API: Revokes the service token with the given ID by deleting it.

REST API: Returns the service tokens for the given workspace, newest first.

REST API: Creates a new service token for the given workspace. The value field is returned exactly once in this response and is never stored — copy it immediately.

REST API: Reports where an approval stands, so an agent holding an approval_required response can wait for the sponsor's decision and retry. Only the agent the approval belongs to can read it.