Respond to an authentication challenge
POST/bv/account/v1/accounts/login:respond-to-challenge
On success, the response has the same shape as NonEmailLoginResponse
with tokens populated. Cognito may (rarely) chain challenges, in which
case challenge_name and session are set on the response and the
caller must invoke this RPC again.
See: https://gitlab.com/blendvision-ai/product-development/-/work_items/170
Request
Responses
- 200
- 400
- 401
- 403
- 500
- default
A successful response.
A unauthenticated response.
The header authorization was missing or unidentified.
A forbidden response.
It means that the provided authorization did not have enough permission to access the resource or the API.
A server error response. There are more HTTP status code mappings listed on here.
An unexpected error response.