Skip to main content
GET
Get Database Certificate
string
required
The ID of the database to retrieve the certificate for.

Response

The response is a JSON object containing the PEM-encoded certificate components for TLS connection to the database, plus the CA and a PKCS#12 bundle when the database has them.
object
The certificate details for secure database connections.

Usage

Every engine requires TLS and the client certificate. Save each field to a file: Use ca.pem (or certificate.pem, which ends with the same CA) as the CA file and, for MongoDB, certificate.pem as the certificate-key file. Use certificate.crt + certificate.key as the client certificate, or certificate.p12 where the driver only accepts a PKCS#12 identity (Prisma 6, with an empty password). The port is unique per database — read it from Get Database. Commands and driver examples for each engine are in How do I connect to each engine?.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • AUTH_TOKEN_MISSING, API_KEY_INVALID, SESSION_REVOKED: The Authorization header is missing, the API key is invalid, or the dashboard session was revoked (401).
  • API_KEY_IP_DENIED, API_KEY_SCOPE_DENIED: The API key is used from an IP outside its allowlist, or it lacks the scope the route requires (403).
  • ACCESS_DENIED: The resource belongs to another account, or you lack the workspace permission for it (403).
  • DATABASE_NOT_FOUND_OR_FORBIDDEN: The specified database does not exist or the user lacks access.
  • FAILED_TO_GET_CERTIFICATE: Failed to retrieve the certificate.
string
A descriptive message providing additional details about the error.
Last modified on October 28, 2026