recourse_answer_invalid: The answer is malformed
The answer must be a dynamo-recourse-answer-v1 statement: the id of this case, a position concede or contest, a 32-byte facts hash or null, and the time it was issued in unix seconds. An answer that names another case is refused too. Nothing was recorded. A body that is not exactly {answer, signature} with a 65-byte signature answers 400 invalid_request first.
What to do
- The answer is malformed (dynamo-recourse-answer-v1: caseId, position concede or contest, factsHash, issuedAt).
On the wire
HTTP 409, error type state_error. Without Dynamo-Error-Detail: 1 every client receives {"error": "state", "reason": "recourse_answer_invalid", "detail": "…"} with no errorDetail: the owner and payee recourse routes add it only when the request sends that header, on a single-tenant core and on the hosted tier alike.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "recourse_answer_invalid",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "recourse_answer_invalid",
"message": "…",
"param": "case",
"doc_url": "…/errors/recourse_answer_invalid.md",
"fix": "the answer is malformed (dynamo-recourse-answer-v1: caseId, position concede or contest, factsHash, issuedAt)"
}
}
See recourse and all error codes.