otp-login-failed-counter
Operations addressed under /otp-login-failed-counter — 2 operations.
get-is-login-otp-blocked-by-phone-number
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as OtpLoginFailDto.
| Field | Declared type | Nullable |
|---|---|---|
FailedCount | int? | yes |
IsBlocked | bool | no |
BlockEndDate | DateTime? | yes |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning |
|---|---|---|
ERR_OTP_17 | 400 | OTP_IS_BLOCKED |
path Parameters
phoneNumberget-is-login-otp-blocked-by-phone-number › Responses
Success. The catalog declares this returns a single record. Of 25 operations in this state with a probeable route, 8 answered and 6 returned a single record — the other two returned a collection and a bare boolean.
blockEndDatefailedCountisBlockedreset-otp-login-failed-count-command-by-phone-number
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
path Parameters
phoneNumberreset-otp-login-failed-count-command-by-phone-number › Responses
Success. The catalog declares no response fields for this operation. The body is UNKNOWN CONTENT. The response type this route registers was read from the service's own source and is published on this operation as x-aura-code-response.