{
  "id": "bdbs",
  "title": "Database requests",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/",
  "summary": "Database requests",
  "content": "\n| Method | Path | Description |\n|--------|------|-------------|\n| [GET](#get-all-bdbs) | `/v1/bdbs` | Get all databases |\n| [GET](#get-bdbs) | `/v1/bdbs/{uid}` | Get a single database |\n| [PUT](#put-bdbs) | `/v1/bdbs/{uid}` | Update database configuration |\n| [PUT](#put-bdbs-action) | `/v1/bdbs/{uid}/{action}` | Update database configuration and perform additional action |\n| [POST](#post-bdbs-v1) | `/v1/bdbs` | Create a new database |\n| [POST](#post-bdbs-v2) | `/v2/bdbs` | Create a new database |\n| [DELETE](#delete-bdbs) | `/v1/bdbs/{uid}` | Delete a database |\n\n## Get all databases {#get-all-bdbs}\n\n```sh\nGET /v1/bdbs\n```\n\nGet all databases in the cluster.\n\n### Permissions\n\n| Permission name | Roles   |\n|-----------------|---------|\n| [view_all_bdbs_info]() |  admin\u003cbr /\u003ecluster_member\u003cbr /\u003ecluster_viewer\u003cbr /\u003edb_member\u003cbr /\u003edb_viewer\u003cbr /\u003euser_manager |\n\n### Request {#get-all-request}\n\n#### Example HTTP request\n\n```sh\nGET /v1/bdbs?fields=uid,name\n```\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n\n#### Query parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| fields | string | Comma-separated list of field names to return (by default all fields are returned). (optional) |\n\n### Response {#get-all-response}\n\nThe response body contains a JSON array with all databases, represented as [BDB objects]().\n\n#### Body\n\n```json\n[\n    {\n        \"uid\": 1,\n        \"name\": \"name of database #1\",\n        \"// additional fields...\"\n    },\n    {\n        \"uid\": 2,\n        \"name\": \"name of database #2\",\n        \"// additional fields...\"\n    }\n]\n```\n\n#### Status codes {#get-all-status-codes}\n\n| Code | Description |\n|------|-------------|\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | No error |\n\n### Example requests\n\n#### cURL\n\n```sh\n$ curl -k -X GET -u \"[username]:[password]\" \\\n       -H \"accept: application/json\" \\\n       https://[host][:port]/v1/bdbs?fields=uid,name\n```\n\n#### Python\n\n```python\nimport requests\nimport json\n\nurl = \"https://[host][:port]/v1/bdbs?fields=uid,name\"\nauth = (\"[username]\", \"[password]\")\n\nheaders = {\n  'Content-Type': 'application/json'\n}\n\nresponse = requests.request(\"GET\", url, auth=auth, headers=headers)\n\nprint(response.text)\n```\n\n## Get a database {#get-bdbs}\n\n```sh\nGET /v1/bdbs/{int: uid}\n```\n\nGet a single database.\n\n#### Permissions\n\n| Permission name | Roles |\n|-----------------|-------|\n| [view_bdb_info]() | admin\u003cbr /\u003ecluster_member\u003cbr /\u003ecluster_viewer\u003cbr /\u003edb_member\u003cbr /\u003edb_viewer\u003cbr /\u003euser_manager |\n\n### Request {#get-request}\n\n#### Example HTTP request\n\n```sh\nGET /v1/bdbs/1\n```\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n\n\n#### URL parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| uid | integer | The unique ID of the database requested. |\n\n\n#### Query parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| fields | string | Comma-separated list of field names to return (by default all fields are returned). (optional) |\n\n### Response {#get-response}\n\nReturns a [BDB object]().\n\n#### Example JSON body\n\n```json\n{\n    \"uid\": 1,\n    \"name\": \"name of database #1\",\n    \"// additional fields...\"\n}\n```\n\n### Status codes {#get-status-codes}\n\n| Code | Description |\n|------|-------------|\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | No error |\n| [404 Not Found](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5) | Database UID does not exist |\n\n## Update database configuration {#put-bdbs}\n\n```sh\nPUT /v1/bdbs/{int: uid}\n```\nUpdate the configuration of an active database.\n\nIf called with the `dry_run` URL query string, the function will validate the [BDB object]() against the existing database, but will not invoke the state machine that will update it.\n\nThis is the basic version of the update request. See [Update database and perform action](#put-bdbs-action) to send an update request with an additional action.\n\nTo track this request's progress, poll the [`/actions/\u003caction_uid\u003e` endpoint]() with the action_uid returned in the response body.\n\n### Permissions\n\n| Permission name | Roles |\n|-----------------|-------|\n| [update_bdb]() | admin\u003cbr /\u003ecluster_member\u003cbr /\u003edb_member |\n\n### Request {#put-request}\n\n#### Example HTTP request\n\n```sh\nPUT /v1/bdbs/1\n```\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n| Content-type | application/json |\n\n#### Query parameters\n\n| Field   | Type | Description |\n|---------|------|---------------|\n| dry_run |      | Validate the new [BDB object]() but don't apply the update. |\n\n#### URL parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| uid | integer | The unique ID of the database for which update is requested. |\n\n#### Body\n\nInclude a [BDB object]() with updated fields in the request body.\n\n##### Example JSON body\n\n```json\n{\n    \"replication\": true,\n    \"data_persistence\": \"aof\"\n}\n```\n\nThe above request attempts to modify a database configuration to enable in-memory data replication and append-only file data persistence.\n\n### Response {#put-response}\n\nReturns the updated [BDB object]().\n\n#### Example JSON body\n\n```json\n{\n    \"uid\": 1,\n    \"replication\": true,\n    \"data_persistence\": \"aof\",\n    \"// additional fields...\"\n}\n```\n\n### Status codes {#put-status-codes}\n\n| Code | Description |\n|------|-------------|\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | The request is accepted and is being processed. The database state will be 'active-change-pending' until the request has been fully processed. |\n| [404\u0026nbsp;Not\u0026nbsp;Found](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5) | Attempting to change a nonexistent database. |\n| [406\u0026nbsp;Not\u0026nbsp;Acceptable](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7) | The requested configuration is invalid. |\n| [409 Conflict](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.10) | Attempting to change a database while it is busy with another configuration change. In this context, this is a temporary condition, and the request should be reattempted later. |\n\n#### Error codes {#put-error-codes}\n\nWhen errors are reported, the server may return a JSON object with    `error_code` and `message` field that provide additional information.    The following are possible `error_code` values:\n\n| Code | Description |\n|------|-------------|\n| rack_awareness_violation | • Non rack-aware cluster.\u003cbr /\u003e• Not enough nodes in unique racks. |\n| invalid_certificate | SSL client certificate is missing or malformed.|\n| certificate_expired | SSL client certificate has expired. |\n| duplicated_certs | An SSL client certificate appears more than once. |\n| insufficient_resources | Shards count exceeds shards limit per bdb. |\n| not_supported_action_on_crdt | `reset_admin_pass` action is not allowed on CRDT enabled BDB. |\n| name_violation | CRDT database name cannot be changed. |\n| bad_shards_blueprint | The sharding blueprint is broken or doesn’t fit the BDB. |\n| replication_violation | CRDT database must use replication. |\n| eviction_policy_violation | LFU eviction policy is not supported on bdb version\u003c4 |\n| replication_node_violation | Not enough nodes for replication. |\n| replication_size_violation | Database limit too small for replication. |\n| invalid_oss_cluster_configuration | BDB configuration does not meet the requirements for OSS cluster mode |\n| missing_backup_interval | BDB backup is enabled but backup interval is missing. |\n| crdt_sharding_violation | CRDB created without sharding cannot be changed to use sharding\n| invalid_proxy_policy | Invalid proxy_policy value. |\n| invalid_bdb_tags | Tag objects with the same key parameter were passed. |\n| unsupported_module_capabilities | Not all modules configured for the database support the capabilities needed for the database configuration. |\n| redis_acl_unsupported | Redis ACL is not supported for this database. |\n\n## Update database and perform action {#put-bdbs-action}\n\n```sh\nPUT /v1/bdbs/{int: uid}/{action}\n```\nUpdate the configuration of an active database and perform an additional action.\n\nIf called with the `dry_run` URL query string, the function will validate the [BDB object]() against the existing database, but will not invoke the state machine that will update it.\n\n#### Permissions\n\n| Permission name | Roles |\n|-----------------|-------|\n| [update_bdb_with_action]() | admin\u003cbr /\u003ecluster_member\u003cbr /\u003edb_member |\n\n### Request {#put-request-action}\n\n#### Example HTTP request\n\n```sh\nPUT /v1/bdbs/1/reset_admin_pass\n```\nThe above request resets the admin password after updating the database.\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n| Content-type | application/json |\n\n#### URL parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| uid | integer | The unique ID of the database to update. |\n| action | string | Additional action to perform. Currently supported actions are: `flush`, `reset_admin_pass`. |\n\n#### Query parameters\n\n| Field   | Type | Description |\n|---------|------|---------------|\n| dry_run |       | Validate the new [BDB object]() but don't apply the update. |\n\n#### Body\n\nInclude a [BDB object]() with updated fields in the request body.\n\n##### Example JSON body\n\n```json\n{\n    \"replication\": true,\n    \"data_persistence\": \"aof\"\n}\n```\n\nThe above request attempts to modify a database configuration to enable in-memory data replication and append-only file data persistence.\n\n\nTo change the shard hashing policy, you must flush all keys from the database.\n\n\n### Response {#put-response-action}\n\nIf the request succeeds, the response body returns the updated [BDB object](). If an error occurs, the response body may include an error code and message with more details.\n\n#### Status codes {#put-status-codes-action}\n\n| Code | Description |\n|------|-------------|\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | The request is accepted and is being processed. The database state will be 'active-change-pending' until the request has been fully processed. |\n| [403\u0026nbsp;Forbidden](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4) | redislabs license expired. |\n| [404\u0026nbsp;Not\u0026nbsp;Found](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5) | Attempting to change a nonexistent database. |\n| [406\u0026nbsp;Not\u0026nbsp;Acceptable](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7) | The requested configuration is invalid. |\n| [409 Conflict](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.10) | Attempting to change a database while it is busy with another configuration change. In this context, this is a temporary condition, and the request should be reattempted later. |\n\n#### Error codes {#put-error-codes-action}\n\nWhen errors are reported, the server may return a JSON object with    `error_code` and `message` field that provide additional information.    The following are possible `error_code` values:\n\n| Code | Description |\n|------|-------------|\n| rack_awareness_violation | • Non rack-aware cluster.\u003cbr /\u003e• Not enough nodes in unique racks. |\n| invalid_certificate | SSL client certificate is missing or malformed.|\n| certificate_expired | SSL client certificate has expired. |\n| duplicated_certs | An SSL client certificate appears more than once. |\n| insufficient_resources | Shards count exceeds shards limit per bdb. |\n| not_supported_action_on_crdt | `reset_admin_pass` action is not allowed on CRDT enabled BDB. |\n| name_violation | CRDT database name cannot be changed. |\n| bad_shards_blueprint | The sharding blueprint is broken or doesn’t fit the BDB. |\n| replication_violation | CRDT database must use replication. |\n| eviction_policy_violation | LFU eviction policy is not supported on bdb version\u003c4 |\n| replication_node_violation | Not enough nodes for replication. |\n| replication_size_violation | Database limit too small for replication. |\n| invalid_oss_cluster_configuration | BDB configuration does not meet the requirements for OSS cluster mode |\n| missing_backup_interval | BDB backup is enabled but backup interval is missing. |\n| crdt_sharding_violation | CRDB created without sharding cannot be changed to use sharding\n| invalid_proxy_policy | Invalid proxy_policy value. |\n| invalid_bdb_tags | Tag objects with the same key parameter were passed. |\n| unsupported_module_capabilities | Not all modules configured for the database support the capabilities needed for the database configuration. |\n| redis_acl_unsupported | Redis ACL is not supported for this database. |\n\n## Create database v1 {#post-bdbs-v1}\n\n```sh\nPOST /v1/bdbs\n```\nCreate a new database in the cluster.\n\nThe request must contain a single JSON [BDB object]() with the configuration parameters for the new database.\n\nThe following parameters are required to create the database:\n\n| Parameter | Type/Value | Description |\n|----------|------------|-------------|\n| name     | string     | Name of the new database |\n| memory_size | integer | Size of the database, in bytes |\n\nIf passed with the `dry_run` URL query string, the function will validate the [BDB object](), but will not invoke the state machine that will create it.\n\nTo track this request's progress, poll the [`/actions/\u003caction_uid\u003e` endpoint]() with the `action_uid` returned in the response body.\n\nThe cluster will use default configuration for any missing database field. The cluster creates a database UID if it is missing.\n\n### Permissions\n\n| Permission name | Roles |\n|-----------------|-------|\n| [create_bdb]() | admin\u003cbr /\u003ecluster_member\u003cbr /\u003edb_member |\n\n### Request {#post-request-v1}\n\n#### Example HTTP request\n\n```sh\nPOST /v1/bdbs\n```\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n| Content-type | application/json |\n\n#### Query parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| dry_run |    | Validate the new [BDB object]() but don't create the database. |\n\n#### Body\n\nInclude a [BDB object]() in the request body.\n\nThe following parameters are required to create the database:\n\n| Paramter | Type/Value | Description |\n|----------|------------|-------------|\n| name     | string     | Name of the new database |\n| memory_size | integer | Size of the database, in bytes |\n\nThe `uid` of the database is auto-assigned by the cluster because it was not explicitly listed in this request. If you specify the database ID (`uid`), then you must specify the database ID for every subsequent database and make sure that the database ID does not conflict with an existing database. If you do not specify the database ID, then the it is automatically assigned in sequential order.\n\nDefaults are used for all other configuration parameters.\n\n#### Example JSON body\n\n```json\n{\n    \"name\": \"test-database\",\n    \"type\": \"redis\",\n    \"memory_size\": 1073741824\n}\n```\n\nThe above request is an attempt to create a Redis database with a user-specified name and a memory limit of 1GB.\n\n### Response {#post-response-v1}\n\nThe response includes the newly created [BDB object]().\n\n#### Example JSON body\n\n```json\n{\n    \"uid\": 1,\n    \"name\": \"test-database\",\n    \"type\": \"redis\",\n    \"memory_size\": 1073741824,\n    \"// additional fields...\"\n}\n```\n\n#### Error codes {#post-error-codes-v1}\n\nWhen errors are reported, the server may return a JSON object with `error_code` and `message` field that provide additional information. The following are possible `error_code` values:\n\n| Code | Description |\n|------|-------------|\n| uid_exists | The specified database UID is already in use. |\n| missing_db_name | DB name is a required property. |\n| missing_memory_size | Memory Size is a required property. |\n| missing_module | Modules missing from the cluster. |\n| port_unavailable | The specified database port is reserved or already in use. |\n| invalid_sharding | Invalid sharding configuration was specified. |\n| bad_shards_blueprint | The sharding blueprint is broken. |\n| not_rack_aware | Cluster is not rack-aware and a rack-aware database was requested. |\n| invalid_version | An invalid database version was requested. |\n| busy | The request failed because another request is being processed at the same time on the same database. |\n| invalid_data_persistence | Invalid data persistence configuration. |\n| invalid_proxy_policy | Invalid proxy_policy value. |\n| invalid_sasl_credentials | SASL credentials are missing or invalid. |\n| invalid_replication | Not enough nodes to perform replication. |\n| insufficient_resources | Not enough resources in cluster to host the database. |\n| rack_awareness_violation | • Rack awareness violation.\u003cbr/\u003e• Not enough nodes in unique racks. |\n| invalid_certificate | SSL client certificate is missing or malformed. |\n| certificate_expired | SSL client certificate has expired. |\n| duplicated_certs | An SSL client certificate appears more than once. |\n| replication_violation | CRDT database must use replication. |\n| eviction_policy_violation | LFU eviction policy is not supported on bdb version\u003c4 |\n| invalid_oss_cluster_configuration | BDB configuration does not meet the requirements for OSS cluster mode |\n| memcached_cannot_use_modules | Cannot create a memcached database with modules. |\n| missing_backup_interval | BDB backup is enabled but backup interval is missing. |\n| wrong_cluster_state_id | The given CLUSTER-STATE-ID does not match the current one\n| invalid_bdb_tags | Tag objects with the same key parameter were passed. |\n| unsupported_module_capabilities | Not all modules configured for the database support the capabilities needed for the database configuration. |\n| redis_acl_unsupported | Redis ACL is not supported for this database. |\n\n#### Status codes {#post-status-codes-v1}\n\n| Code | Description |\n|------|-------------|\n| [403 Forbidden](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4) | redislabs license expired. |\n| [409 Conflict](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.10) | Database with the same UID already exists. |\n| [406 Not Acceptable](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7) | Invalid configuration parameters provided. |\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | Success, database is being created. |\n\n## Create database v2 {#post-bdbs-v2}\n\n```sh\nPOST /v2/bdbs\n```\nCreate a new database in the cluster. See [`POST /v1/bdbs`]() for more information.\n\nThe database's configuration should be under the \"bdb\" field.\n\nThis endpoint allows you to specify a recovery_plan to recover a database. If you include a recovery_plan within the request body, the database will be loaded from the persistence files according to the recovery plan. The recovery plan must match the number of shards requested for the database.\n\nThe persistence files must exist in the locations specified by the recovery plan. The persistence files must belong to a database with the same shard settings as the one being created (slot range distribution and shard_key_regex); otherwise, the operation will fail or yield unpredictable results.\n\nIf you create a database with a shards_blueprint and a recovery plan, the shard placement may not fully follow the shards_blueprint.\n\n### Request {#post-request-v2}\n\n#### Example HTTP request\n\n```sh\nPOST /v2/bdbs\n```\n\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n| Content-type | application/json |\n\n#### Query parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| dry_run |    | Validate the new [BDB object]() but don't create the database. |\n\n#### Body\n\nInclude a JSON object that contains a [BDB object]() and an optional `recovery_plan` object in the request body.\n\n##### Example JSON body\n\n```json\n{\n    \"bdb\": {\n        \"name\": \"test-database\",\n        \"type\": \"redis\",\n        \"memory_size\": 1073741824,\n        \"shards_count\": 1\n    },\n    \"recovery_plan\": {\n        \"data_files\": [\n            {\n                \"shard_slots\": \"0-16383\",\n                \"node_uid\": \"1\",\n                \"filename\": \"redis-4.rdb\"\n            }\n        ]\n    }\n}\n```\n\n### Response {#post-response-v2}\n\nThe response includes the newly created [BDB object]().\n\n#### Example JSON body\n\n```json\n{\n    \"uid\": 1,\n    \"name\": \"test-database\",\n    \"type\": \"redis\",\n    \"memory_size\": 1073741824,\n    \"shards_count\": 1,\n    \"// additional fields...\"\n}\n```\n\n## Delete database {#delete-bdbs}\n\n```sh\nDELETE /v1/bdbs/{int: uid}\n```\nDelete an active database.\n\n### Permissions\n\n| Permission name | Roles |\n|-----------------|-------|\n| [delete_bdb]() | admin\u003cbr /\u003ecluster_member\u003cbr /\u003edb_member |\n\n### Request {#delete-request}\n\n#### Example HTTP request\n\n```sh\nDELETE /v1/bdbs/1\n```\n#### Headers\n\n| Key | Value |\n|-----|-------|\n| Host | The domain name or IP of the cluster |\n| Accept | application/json |\n\n#### URL parameters\n\n| Field | Type | Description |\n|-------|------|-------------|\n| uid | integer | The unique ID of the database to delete. |\n\n### Response {#delete-response}\n\nReturns a status code that indicates the database deletion success or failure.\n\n### Status codes {#delete-status-codes}\n\n| Code | Description |\n|------|-------------|\n| [200 OK](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) | The request is accepted and is being processed. The database state will be 'delete-pending' until the request has been fully processed. |\n| [403 Forbidden](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4) | Attempting to delete an internal database. |\n| [404\u0026nbsp;Not\u0026nbsp;Found](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5) | Attempting to delete a nonexistent database. |\n| [409 Conflict](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.10) | Either the database is not in 'active' state and cannot be deleted, or it is busy with another configuration change. In the second case, this is a temporary condition, and the request should be re-attempted later. |\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00",
  "children": [{"id":"actions","summary":"Database action requests","title":"Database actions requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/actions/"},{"id":"alerts","summary":"Database alert requests","title":"Database alerts requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/alerts/"},{"id":"availability","summary":"REST API requests to check database availability","title":"Database availability requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/availability/"},{"id":"crdt_sources-alerts","summary":"Conflict-free replicated data type (CRDT) source alert requests","title":"Database CRDT sources alerts requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/crdt_sources-alerts/"},{"id":"debuginfo","summary":"Documents the Redis Enterprise Software REST API /bdbs/debuginfo requests.","title":"Database debug info requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/debuginfo/"},{"id":"modules","summary":"Redis module requests","title":"Database modules requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/modules/"},{"id":"passwords","summary":"Database password requests","title":"Database passwords requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/passwords/"},{"id":"peer_stats","summary":"Active-Active peer instance statistics requests","title":"CRDB peer stats requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/peer_stats/"},{"id":"replica_sources-alerts","summary":"Replica source alert requests","title":"Database replica sources alerts requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/replica_sources-alerts/"},{"id":"shards","summary":"REST API requests for database shards","title":"Database shards requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/shards/"},{"id":"stats","summary":"Database statistics requests","title":"Database stats requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/stats/"},{"id":"sync_source_stats","summary":"Syncer source statistics requests","title":"Database syncer source stats requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/sync_source_stats/"},{"id":"syncer_state","summary":"Syncer state requests","title":"Syncer state requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/syncer_state/"},{"id":"upgrade","summary":"Database upgrade requests","title":"Database upgrade requests","url":"https://redis.io/docs/latest/operate/rs/7.8/references/rest-api/requests/bdbs/upgrade/"}]
}