Even a newly generated api_key is not getting validated when I check using nixtla_client.validate_api_key(). What could be the cause of this error? I am currently in the trial period for timeGPT. I'd appreciate any help regarding this issue. Thanks!

Thanks @Apoorv Khanuja for reporting, and sorry it's not working. Things look ok on our side. Is it possible anything has changed with your firewall settings that's limiting access to our API?

Thanks for the quick response @Tracy Teal. I haven't messed around with the firewall settings at all. I'm currently testing the code on google colab (before incorporating it into a separate software via docker - but I haven't even gotten to this stage yet). Do you have any ideas on how I could resolve this? I'll appreciate any assistance you could provide. Thanks.

Thanks, that's helpful to know you're on collab. I'll look into that. It shouldn't be a billing issue. Was it working before on collab, and now it's not?

Yes, the old API key was working on Colab before, but now neither the old one nor the newly generated keys are working/validating

Thanks, that's really helpful. We're looking into this. Do you have a request ID you could share?

@Tracy Teal Since the request is not erroring out, I don't have a request ID.

nixtla_client.validate_api_key()

simply returns False and these requests aren't even showing up on my dashboard. Is there a way I can get the request ID without it erroring out?

Right, of course, thanks. I was able to replicate this issue. API keys work locally, but not on Colab. We're looking into this and working on a fix, so I'll keep you updated. Thanks so much for reporting and working with us on troubleshooting.

That's interesting. Did something happen recently? Because I was able to use the API keys in Colab till last week. I can work on my local machine in the meantime. Please let me know when this issue gets resolved. Thanks!

Thanks, we'll look into this as well.

Awesome! Thanks for the quick resolution. The API key is working again on both colab and within docker. If you don't mind me asking, what caused this issue?

Thanks, that's great to hear. It was an issue in our middleware. We fixed and added a test, so we would catch this in the future.