I don’t think that URL is correct.
Should be something like https://identitytoolkit.googleapis.com/…
e.g in docs here
https://identitytoolkit.googleapis.com/v1/accounts:sendOobCode?key=[API_KEY]
Perhaps verify your config is correct and has the right Auth providers associated.
here is link to this part of docs:
fetch-providers-for-email
Of course the function you are calling is documented here:
getOobConfirmationCode
However, this is to allow auth using the users google account, which is a different usecase and implementation to firebase auth, where users signup and provide account details.
Not just a case of (very easily!) wires crossed as to which API you have implemented vs should be using?
@MarketForce
Didn’t got what you are saying…
Your topic title says 404, but your OP says 400. Which is it? They’re completely different errors with completely different causes. 404 is attempting to access something that doesn’t exist, 400 is feeding the backend food it can’t or doesn’t want to eat.