Phone Not Verified

phone-not-verified · 402

The account has no verified phone number, which deploying needs, so the API changed nothing.

For a launch or a deploy, the number checked is the organization owner's. A number is verified on the Ghaym account page at accountUrl, not through the Cloud API.

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

Common causes

  • The organization's owner signed up but never entered the code sent by SMS.

How to fix the call

  • Tell the user to verify a number at accountUrl: it's theirs to do, with a code sent by SMS.
  • Read what stands in the way with ghaym cloud billing eligibility, or GET /v1/billing/eligibility, before trying again.
  • Don't retry before the number is verified: the answer won't change.

Example response

json
{
  "type": "phone-not-verified",
  "title": "Phone Not Verified",
  "detail": "This account has no verified phone number, which is required before anything can be deployed. Verify one on the Ghaym account page at https://auth.ghaym.me/account. Check readiness up front with GET /v1/billing/eligibility.",
  "accountUrl": "https://auth.ghaym.me/account",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "status": 402,
  "docs": "https://ghaym.me/docs/errors/phone-not-verified"
}