# Failed Logins: Missing required parameter: response\_type

**URL:** <https://community.auth0.com/t/failed-logins-missing-required-parameter-response-type/164400>\
**Category:** Get Help\
**Tags:** classic-universal-login-experience, login-experience\
**Created:** [December 19, 2024, 10:06am UTC](https://community.auth0.com/t/failed-logins-missing-required-parameter-response-type/164400 "2024-12-19T10:06:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric12](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/eric12/32/40864_2.png) [@eric12](https://community.auth0.com/u/eric12)\
**Post date:** [December 19, 2024, 10:06am UTC](https://community.auth0.com/t/failed-logins-missing-required-parameter-response-type/164400/1 "2024-12-19T10:06:15Z")

</div>

Hello,

I am receiving a number of failed logins, intermixed with normal/successful logins. The failed logins come in ‘bursts’ of 6-8 at a time, all within a few seconds of each other, and all with the same description: “Missing required parameter: response\_type”

These failed logins also do not have an assigned Application or Connection - they all say “N/A”, whereas the successful logins all have their correct designations listed.

Here is a support topic with a similar scenario: [Missing required parameter: response\_type - #11](https://community.auth0.com/t/missing-required-parameter-response-type/75629/11)

This feels a bit like a series of bot/spam login attempts, but am uncertain how to verify this or go about restricting them. Any advice would be appreciated.

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [December 19, 2024, 9:45pm UTC](https://community.auth0.com/t/failed-logins-missing-required-parameter-response-type/164400/3 "2024-12-19T21:45:42Z")

</div>

Hi @eric12,

I understand you encountered the `“Missing required parameter: response_type”` error.

I have reproduced this issue by omitting the `response_type` in the login request. As you have observed, the application and connection are N/A.

In this scenario, you must ensure the login requests include the `response_type` query parameter.

For example:

```auto
https://{yourDomain}/authorize?
    response_type=code&
    client_id={yourClientId}&
    redirect_uri={https://yourApp/callback}&
    scope={scope}&
    audience={apiAudience}&
    state={state}

```

(Reference: [Call Your API Using the Authorization Code Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/call-your-api-using-the-authorization-code-flow))

I can guarantee that this is unrelated to bot/spam login attempts because it refers to a missing query parameter. If this were bot/spam activity, you would see scripted login/signup attacks, which you can workaround by enabling the features for [Attack Protection](https://auth0.com/docs/secure/attack-protection).

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 2, 2025, 9:46pm UTC](https://community.auth0.com/t/failed-logins-missing-required-parameter-response-type/164400/4 "2025-01-02T21:46:30Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
