Skip to content
1 minute readFixedAgent-ready

Claim errors name a reason code

Every refusal from POST /api/agents/claim now carries a code, a server failure carries a reference for support, and the claim page shows both and lets you retry instead of saying the workspace cannot be claimed.

When a claim failed, the claim page said "This workspace cannot be claimed" with a generic "Claim failed" line, and the API gave no code to tell a broken link from a passing server error.

  • Every error from POST /api/agents/claim has a code: claim_link_invalid (unknown or used link), claim_link_expired, claim_cross_site, claim_rate_limited, claim_unavailable, invalid_request for a malformed body, and claim_failed for an unexpected server error. The existing codes (claim_cap_reached, claiming_workspace_ineligible and the rest) are unchanged.
  • A claim_failed answer also carries a reference, logged with the error on our side. Quote it to support@last-price.ai and we can find what went wrong.
  • On the claim page, a server error or a busy moment keeps the preview up with the code and reference and a "Try the claim again" button. A link that cannot be used still ends the page, now with its code.
  • The server error behind most of these reports is already fixed (see "Claiming an agent workspace works again").