Backups Not Supported

backups-unsupported · 422

Backups cover managed PostgreSQL and MySQL databases only, and this service is something else, so the API took no backup.

Reading a service's backups never answers this: the answer's supported says whether backups cover the service. serviceId names the service that was refused.

Besides the members every error carries, this type adds serviceId.

Common causes

  • The service is a web service.
  • The service is a Redis cache, and backups don't cover caches.
  • The call named the wrong service: serviceId is the one it reached.

How to fix the call

  • Read supported from GET /v1/services/<id>/backups before offering a backup.
  • If the call meant a PostgreSQL or MySQL database, send its id instead.
  • Don't retry: a service's type doesn't change.

Example response

json
{
  "type": "backups-unsupported",
  "title": "Backups Not Supported",
  "detail": "Backups cover managed PostgreSQL and MySQL databases only.",
  "serviceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups",
  "status": 422,
  "docs": "https://ghaym.me/docs/errors/backups-unsupported"
}