-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad Response (Forefront gives Stream Respnse) #4
Comments
after i hardcoded the API key into the emailFactory, the Request just dies with 403 |
data: { message: 'Request failed with status code 403' } |
Is the full error stack i get |
Yea with tinkering i got it to atleast create mails. Now clerk is complaining about too many requests from the machine. Any idea on how many requests u can make? |
look like your rapid_api_key ia wrong |
you can config it in .env |
i think you donot subscribe email api |
Yea, no. After massive amounts of tinkering I somehow got it to work after
some time.
And got my machine blacklisted from the clerk thingy yesterday. Imma hope
it works today again.
|
how do you know you are in blacklist. what reponse when in black |
It just told me that i had too many Requests from a Machine.
|
The Commit in #8 includes a "Logger" of some sort that sends the error code on why the Token Parser did not work. There it showed me that i had too many requests. |
that because TempEmail44 limit 100/day, if you have credit card, you can change email to TempEmail without '44' |
Yea now it has the issue with the stream response |
This is not completed? I still have the response issue |
https://tay.needs.rest/notepad_RIBQXT2O6v.png
https://tay.needs.rest/Code_Z6Tt7c4M0W.png
The text was updated successfully, but these errors were encountered: