Is this another dead product? | Fireapis | AppSumo

Fireapis

Product details

megaquests

Apr 26, 2026

Q: Is this another dead product? I bought 3 codes

Domain is dead

Share

Helpful?

0

Log in to join the conversation

Related questions

Reached out for support and got nothing back in return. Refunded... Hopefully, they will improve and win some doubters back.
Wondering if there is any SUPPORT for this product. It's been more than a week - and had a simple setup question. The response was that their system is down. Is it down FOREVER? I hope to get the answer - as well as a solution to my problem. If I don't hear, you know what should happen.
I've got the T3, and I'm very excited about this no-code API creation platform. I do have some concerns that I want to get some answers to: 1. Why is the playground requests counting towards the total account quota? 2. I created the Fireapis Authentication API and played with it and then decided to delete it to start from scratch, and to my surprise, it just returned with the same data as I already had created with in the previous once? - not deleted at all!! 3. I get some 500 internal errors. That's concerning if I want to put this into production, I need to be 110% sure that requests will not get these internal errors. Btw. It's a shame that failed requests count towards the quota when the platform reports these internal error issues. I look forward to continuing to play around with Fireapis and keep testing its potential. I hope you will answer my questions and fix the issues so it's more stable and reliable. Btw. a suggestion. It would be nice to have a support contact form inside the platform that could be used to send requests, issues, and support requests, instead of needing to find email on the website or asking questions on AppSumo ;-)
Can this be also used in a production environment. Or is this just to create a dummy / proof or concept application. The reason I'm asking because I've gone through all documentation and samples. And seems that you create CRUD operation for an entity for instance "Product". And then you use a GET to retrieve products and post to INSERT/ADD products. BUT, and this is a very big BUT, everyone who has acces to GET data, can also use the same connection to POST data or add products. Meaning it's worthless for real live production purposes where you would have readonly acces to the general public and modify access to only certain users. Hope this question gets to you in time, because it's only a few hours left before the LTD ends. But being able to seperate access between GET and POST operation would be a deal breaker for my purposes if this is not possible.

View product details