Plan Not Found

plan-not-found · 404

An operator route found no plan by that identifier.

Only operators reach the routes that send it. resourceId repeats the identifier the API looked up.

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

Common causes

  • The identifier is wrong: it matches no record.
  • The plan exists but nothing of it is on sale, which answers the same 404.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "plan-not-found",
  "title": "Plan Not Found",
  "detail": "Plan with ID 'ghaym-s9' was not found",
  "resourceType": "Plan",
  "resourceId": "ghaym-s9",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/admin/instances",
  "method": "POST",
  "instance": "POST /v1/admin/instances",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/plan-not-found"
}