How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

YugabyteDB Disaster Recovery API

The Disaster Recovery API from YugabyteDB — 15 operation(s) for disaster recovery.

This API exposes 16 operations across 15 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, /.

16 operations 15 paths 21 schemas 1 DELETE2 GET12 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://cloud.yugabyte.com/api/public/v1
Authentication
API Key
Contact
https://docs.yugabyte.com
Terms of Service
Resource Areas
1

Authentication & Security 1

YugabyteDB Disaster Recovery API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-AUTH-YW-API-TOKEN (apiKeyAuth).

  • apiKeyAuth — API token passed as header

Paths & Operations 16

Across 15 paths, the API surfaces 16 operations — 1 DELETE, 2 GET, 12 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Disaster Recovery 16
POST
/api/v1/customers/{cUUID}/dr_configs
Create disaster recovery config
createDrConfig 2 params body → 200
DELETE
/api/v1/customers/{cUUID}/dr_configs/{drUUID}
Delete xcluster config
deleteXClusterConfig 4 params → 200
GET
/api/v1/customers/{cUUID}/dr_configs/{drUUID}
Get disaster recovery config
getDrConfig 3 params → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/edit
Edit disaster recovery config
editDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/failover
Failover a disaster recovery config
failoverDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/pause
Pause DR config
pauseDrConfig 3 params → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/pause_universes
Pause DR config and universes associated with DR
pauseDrUniverses 3 params → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/replace_replica
Replace Replica in a disaster recovery config
replaceReplicaDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/restart
Restart disaster recovery config
restartDrConfig 4 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/resume
Resume DR config
resumeDrConfig 3 params → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/resume_universes
Resume DR config and universes associated with DR
resumeDrUniverses 3 params → 200
GET
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/safetime
Get disaster recovery config safetime
getDrConfigSafetime 2 params → 200
PUT
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/set_dbs
Set databases in disaster recovery config
setDatabasesDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/set_tables
Set tables in disaster recovery config
setTablesDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/switchover
Switchover a disaster recovery config
switchoverDrConfig 3 params body → 200
POST
/api/v1/customers/{cUUID}/dr_configs/{drUUID}/sync
Sync disaster recovery config
syncDrConfig 3 params → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are DrConfigGetResp (29 properties), TableInfoResp (16 properties), PitrConfig (16 properties), XClusterTableConfig (13 properties). Each schema is shown below with its type and property counts.

DrConfigSetTablesForm
object
dr config set tables form
3 properties
RestartBootstrapParams
object
Bootstrap parameters for restarting
1 property 1 required
DrConfigEditForm
object
drConfig edit form
3 properties
DrConfigSetDatabasesForm
object
dr config set databases form
1 property
PitrConfig
object
PITR config created on the universe
16 properties 3 required
YBPTask
object
2 properties
GetWebhookResponse
object
Webhook get response
2 properties
XClusterNamespaceConfig
object
7 properties 3 required
DrConfigFailoverForm
object
drConfig failover form
3 properties
DrConfigSwitchoverForm
object
drConfig failover form
2 properties
NamespaceSafetime
object
6 properties 6 required
PitrParams
object
PITR parameters
2 properties
DrConfigRestartForm
object
dr config restart form
2 properties 1 required
DrConfigReplaceReplicaForm
object
drConfig edit form
3 properties
BootstrapBackupParams
object
Backup parameters for bootstrapping
2 properties 1 required
NamespaceInfoResp
object
Namespace information response
3 properties
DrConfigCreateForm
object
drConfig create form
7 properties 4 required
DrConfigSafetimeResp
object
Get DR config safetime response
1 property
XClusterTableConfig
object
13 properties 2 required
TableInfoResp
object
Table information response
16 properties
DrConfigGetResp
object
disaster recovery get response
29 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yugabytedb-disaster-recovery-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of YugabyteDB Disaster Recovery API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.