> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/api-reference/databases/v2-1/overview.md).

# Overview

The IONOS CLOUD DBaaS MariaDB v2 API provides a REST interface for provisioning and managing MariaDB clusters. It features dedicated backup location management, a declarative restore model, and granular lifecycle states compared to the v1 API. If you are new to the MariaDB v2 API, see [What Can You Do with the MariaDB v2 API?](#section/Overview/What-Can-You-Do-with-the-MariaDB-v2-API). If you are migrating from v1, see [MariaDB API Versions](#tag/MariaDB-API-Versions).

### What Can You Do with the MariaDB v2 API?

The IONOS CLOUD MariaDB v2 API provides a developer-friendly interface to manage the full lifecycle of your MariaDB clusters. Using the v2 API, you can:

* **Provision and modify clusters:** Safely create or update your MariaDB deployments using the idempotent Ensure pattern (`PUT` semantics) on region-specific endpoints.
* **Control backup data residency:** Query dedicated backup location resources to determine where your Point-in-Time Recovery (PITR) backups are stored and plan for data residency requirements.
* **Retrieve PITR backups:** Access and filter your backups as a first-class resource through the `/backups` endpoint, with recovery windows for Point-in-Time Recovery.
* **Query supported versions:** Retrieve centralized lists of supported MariaDB versions, their lifecycle status, and available upgrade paths.
* **Search and filter resources:** Filter clusters by name and state, and filter backups by cluster ID (`filter.clusterId`), alongside standardized pagination across listing endpoints.

### Endpoints

The MariaDB v2 APIs are available with the following API endpoints.

| **Location**              | **Region** | **Endpoint**                          |
| ------------------------- | ---------- | ------------------------------------- |
| Berlin, Germany           | `de-txl`   | `https://mariadb.de-txl.ionos.com/v2` |
| Frankfurt, Germany        | `de-fra`   | `https://mariadb.de-fra.ionos.com/v2` |
| Paris, France             | `fr-par`   | `https://mariadb.fr-par.ionos.com/v2` |
| Logroño, Spain            | `es-vit`   | `https://mariadb.es-vit.ionos.com/v2` |
| London, United Kingdom    | `gb-lhr`   | `https://mariadb.gb-lhr.ionos.com/v2` |
| Worcester, United Kingdom | `gb-bhx`   | `https://mariadb.gb-bhx.ionos.com/v2` |
| Las Vegas, United States  | `us-las`   | `https://mariadb.us-las.ionos.com/v2` |
| Lenexa, United States     | `us-mci`   | `https://mariadb.us-mci.ionos.com/v2` |
| Newark, United States     | `us-ewr`   | `https://mariadb.us-ewr.ionos.com/v2` |

To authenticate with the API, see [Authentication](#tag/Authentication). To make your first API call, see [Quick Start](#tag/Quick-Start).

### Features

* **Storage:** MariaDB v2 uses SSD Premium as the standard storage type for optimal IOPS performance. HDD and SSD Standard storage types are unavailable for MariaDB v2.
* **Ensure pattern:** `PUT` operations use full-replacement semantics. All required cluster fields must be present in every `PUT` request. Any field omitted is set to its schema default or cleared to empty — it does not retain its previous value.
* **Asynchronous operations:** Create, update, and delete operations are asynchronous. Poll `metadata.state` (`PROVISIONING`, `AVAILABLE`, `UPDATING`, `DESTROYING`, `FAILED`) before proceeding.

### Benefits

* **Geographic backup control:** The BackupLocations resource enables you to explicitly select where IONOS CLOUD stores PITR backups across Object Storage regions. You can separate backup storage from your cluster region to meet data residency or disaster recovery requirements.
* **Declarative restore model:** The `restoreFromBackup` object inside the cluster configuration declares restore intent as part of the cluster lifecycle. You do not need a separate restore endpoint or tag. New clusters and in-place recoveries use the same familiar cluster operations.
* **Observability setup:** The `logsEnabled` and `metricsEnabled` flags on the cluster object route logs and metrics to IONOS CLOUD observability services. You configure observability as part of provisioning without managing a separate integration endpoint.
* **Integrated credential management:** The `credentials` object on the cluster creates the primary database user and initial database in a single provisioning step. You do not need separate user or database endpoint calls after the cluster is available.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/api-reference/databases/v2-1/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.