databases
GET /v1/databases/catalogue
The managed-database sizes and engine versions on sale.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/databases/catalogue \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
What may be bought right now, per engine. Gated on `databases.view`. Each engine's versions are served from its own fence, so a major approaching end of life disappears from the picker with no frontend change — we stop selling one 180 days before upstream stops patching it, because a customer part-way through a term must never be stranded on an unpatched engine. MySQL 8.0 is the one exception and it says so: it is past upstream end of life, offered under a recorded carve-out on Percona's patched build, and flagged `past_upstream_eol` so a customer choosing it knows what they are choosing.
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
engines | ManagedDatabaseEngineOffer[] | 是 | — |
default_engine | string<postgres, mysql> | 是 | — |
sizes | ManagedDatabaseSize[] | 是 | The default engine's ladder. Use `engines[].sizes`. |
engine_versions | ManagedDatabaseEngineVersion[] | 是 | The default engine's versions. Use `engines[].versions`. |
default_engine_version | integer | 是 | — |
此端点可能返回的错误
401 · 403