CHANGE_UNCONFIRMED - Blujay API

HTTP status	Retryable
`503`	Yes

What happened

The phone number did not confirm the edit or unsend in time. It may or may not have applied.

How to fix it

Retry with the same idempotency key. Blujay checks whether the change already applied before trying again.

This error is safe to retry. Wait for the Retry-After header when it is present. If the endpoint takes an Idempotency-Key, reuse the same key so a retry never creates a duplicate.

Example response

An illustrative example. The message wording and the contents of details vary; branch on error.code.

{
  "status": "error",
  "error": {
    "code": "CHANGE_UNCONFIRMED",
    "message": "Change not confirmed",
    "type": "phone_number",
    "http_status": 503,
    "retryable": true,
    "doc_url": "https://docs.blujay.io/errors/change-unconfirmed",
    "details": []
  },
  "trace_id": "trc_8f2a1c0e4b7d",
  "timestamp": "2026-10-14T17:30:48.000Z"
}

Still stuck?

Email support@blujay.io with the trace_id from the error response. See Errors for the response format.