> ## Documentation Index > Fetch the complete documentation index at: https://api-docs.sevalla.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > This is the Sevalla REST API reference. Base URL: https://api.sevalla.com/v3. Authenticate with an API key in the Authorization header as a Bearer token. > The OpenAPI spec is at https://api.sevalla.com/v3/openapi.json. Concepts and dashboard guides are at https://docs.sevalla.com (index: https://docs.sevalla.com/llms.txt). > To act on a Sevalla account from an AI agent, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md) or the Sevalla CLI (https://api-docs.sevalla.com/v3/cli.md). # Enable database TLS > Turn on TLS for a database on an OCI cluster that was created without it. Databases created on OCI clusters have TLS from the start. Plaintext connections keep working inside the cluster and, for PostgreSQL, MySQL and MariaDB, through the external connection, so existing applications are not affected. On Redis and Valkey the external connection then requires TLS: external clients have to switch to `rediss://` with the CA certificate. TLS cannot be turned off again. The operation is asynchronous and restarts the database once: the status is `updating` until it is back to `ready`, and then `tls_enabled` is true and `tls_ca_certificate` holds the CA certificate on the Get Database endpoint. Calling it on a database with TLS already on changes nothing. Allowed only when the database status is `ready` and the database is not suspended. ## OpenAPI ````yaml https://api.sevalla.com/v3/openapi.json post /databases/{id}/tls/enable openapi: 3.1.0 info: title: Sevalla API docs version: 1.0.0 servers: - url: https://api.sevalla.com/v3 security: - bearerAuth: [] paths: /databases/{id}/tls/enable: post: tags: - Databases summary: Enable database TLS description: >- Turn on TLS for a database on an OCI cluster that was created without it. Databases created on OCI clusters have TLS from the start. Plaintext connections keep working inside the cluster and, for PostgreSQL, MySQL and MariaDB, through the external connection, so existing applications are not affected. On Redis and Valkey the external connection then requires TLS: external clients have to switch to `rediss://` with the CA certificate. TLS cannot be turned off again. The operation is asynchronous and restarts the database once: the status is `updating` until it is back to `ready`, and then `tls_enabled` is true and `tls_ca_certificate` holds the CA certificate on the Get Database endpoint. Calling it on a database with TLS already on changes nothing. Allowed only when the database status is `ready` and the database is not suspended. operationId: enableDatabaseTlsV3 parameters: - schema: example: fb5e5168-4281-4bec-94c5-0d1584e9e657 type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ in: path name: id required: true description: Database identifier responses: '202': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Confirmation message example: Database TLS enabling started required: - message additionalProperties: false '400': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: Bad request status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 400 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: Unauthorized status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 401 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: >- This API key is missing the : permission. Grant it to the key or use a key that has it. status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 403 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false '404': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: Not found status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 404 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false '429': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: Too many requests status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 429 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false '500': description: Default Response content: application/json: schema: type: object properties: message: type: string description: Error message example: Internal Server Error status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: HTTP status code example: 500 data: type: object properties: code: description: Error tracking code for support reference example: err-abc-123 type: string message: description: Additional error details or instructions example: >- If you need assistance, please contact support and provide this error code. type: string additionalProperties: false required: - message - status additionalProperties: false components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- API key authentication. Pass your API key as a Bearer token in the Authorization header. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.