post-accounts-USERNAME-challenge-CHALLENGE_ID-confirm.rst (1141B)
1 .. http:post:: /accounts/$USERNAME/challenge/$CHALLENGE_ID/confirm 2 3 Solves the ``CHALLENGE_ID`` challenge and allows performing the protected operation. 4 5 When the challenge is confirmed, you can call the protected endpoint again with ``CHALLENGE_ID`` in the ``Taler-Challenge-Ids`` HTTP header and an the original request body. 6 7 This endpoints is not authenticated. Too many unsuccessful attempts to confirm token creation challenges block the account. 8 9 **Request:** 10 11 .. ts:def:: ChallengeSolve 12 13 interface ChallengeSolve { 14 // The TAN code that solves $CHALLENGE_ID 15 tan: string; 16 } 17 18 **Response:** 19 20 :http:statuscode:`204 No Content`: 21 The challenge is confirmed. 22 :http:statuscode:`404 Not Found`: 23 * ``TALER_EC_BANK_TRANSACTION_NOT_FOUND`` : unknown challenge TAN. 24 * ``TALER_EC_BANK_TAN_CHALLENGE_EXPIRED`` : expired challenge. 25 :http:statuscode:`409 Conflict`: 26 * ``TALER_EC_BANK_TAN_CHALLENGE_FAILED`` : wrong TAN. 27 * ``TALER_EC_BANK_TAN_CHALLENGE_EXPIRED`` : expired TAN. 28 :http:statuscode:`429 Too many requests`: 29 Too many failed confirmation attempts, a new TAN must be requested.