Region Not Found

region-not-found · 404

The API offers no region by that key.

The catalogue is the same for every workspace, so this is about the key, not about access. resourceId repeats the key the API looked up. A region is found by its slug, such as amman-1, whatever its status.

Besides the members every error carries, this type adds resourceType and resourceId.

Common causes

  • The key is wrong or made up.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • Send a key from ghaym cloud regions list.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "region-not-found",
  "title": "Region Not Found",
  "detail": "Region with ID 'eu-central-1' was not found",
  "resourceType": "Region",
  "resourceId": "eu-central-1",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/regions/eu-central-1/sizes",
  "method": "GET",
  "instance": "GET /v1/regions/eu-central-1/sizes",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/region-not-found"
}