link_challenge: The link proof does not answer a live challenge
A two_key, web_bot_auth or a2a_card link (POST /owner/v1/accounts/:id/links) signs a dynamo-account-link-v2 challenge that this deployment issued, and the challenge it signs is not live: it was never issued for this account and proof type, it was already used, or it has expired (challenges last 300 seconds and link once). Nothing was linked and the account's level is unchanged.
A challenge the client wrote itself (the earlier dynamo-account-link: text) is refused at every Dynamo-Version with proof_invalid, as is a challenge issued for another proof type, address or deployment.
What to do
- Fetch a new challenge:
POST /owner/v1/link-challengeswith{ "accountId": "acct_…", "proofType": "two_key" }(orweb_bot_auth,a2a_card), pinned atDynamo-Version1.9.0 or later. The answer'schallenge.messageis the exact text to sign. - Sign that text unchanged (both keys for
two_key; the Web Bot Auth key forweb_bot_auth; fora2a_card, put it in the card'schallengefield) and link within 300 seconds.
On the wire
HTTP 400, error type invalid_request_error. Every client gets errorDetail, with or without Dynamo-Error-Detail: 1. A client pinned before Dynamo-Version 1.8.0 (on a single-tenant core, also one that names no version) gets the earlier doc_url form: the docs base followed by /errors/link_challenge.md (with the default docs base, a doubled errors/errors/ path).
{
"error": "link_challenge",
"errorDetail": {
"type": "invalid_request_error",
"code": "link_challenge",
"message": "the challenge is not a live dynamo-account-link-v2 challenge of this account for this proof type (unknown, used or expired)",
"param": "challenge",
"doc_url": "…/errors/link_challenge.md",
"fix": "fetch a new challenge (POST /owner/v1/link-challenges with this proofType) and sign it within 300 s; a challenge links once"
}
}
See all error codes.