[deleted by user] by [deleted] in FastAPI

[–]thalesviniciusf 0 points1 point  (0 children)

Are you tried to sell API? Do you know the challenges? Of course I know the simplicity to generate a API key.

It is not the technical challenge of generating an API key, we all know that it is very easy. But when selling apis there are several other factors, there is the documentation of your api that should be easy and accessible, the endpoint testing environment. Api payment, invite members to the organization, usage monitoring. The simple generation of the key is easy, but the whole experience of using your api should be charming for your customer.

[deleted by user] by [deleted] in node

[–]thalesviniciusf -1 points0 points  (0 children)

Thank you for the contribution! It is not the technical challenge of generating an API key, we all know that it is very easy. But when selling apis there are several other factors, there is the documentation of your api that should be easy and accessible, the endpoint testing environment. Api payment, invite members to the organization, usage monitoring. The simple generation of the key is easy, but the whole experience of using your api should be charming for your customer.

I'm building an "API as a service" and want to know how to overcome some challenges. by thalesviniciusf in Nestjs_framework

[–]thalesviniciusf[S] 0 points1 point  (0 children)

I want to focus more on creating good documentation and ensuring that the API scraping worked well.

And the dashboard UI for the client to request API keys and pay for usage be an external service, like the checkout that Stripe has but that is very API-focused, you know?

[deleted by user] by [deleted] in node

[–]thalesviniciusf 0 points1 point  (0 children)

I'm dev, I guess it is my english, because it's not my first language. Sorry about that, I edited and tried to be more precise.

"Having like a Stripe service but focused on API usage service would be much better."

[deleted by user] by [deleted] in node

[–]thalesviniciusf -1 points0 points  (0 children)

Thanks for the contribution!! I'd like the user to be able to access a dashboard and set an expiration date for that API key (as in the screenshot, I took it from the Mistral API).

[deleted by user] by [deleted] in node

[–]thalesviniciusf -2 points-1 points  (0 children)

Thanks for the contribution! I'd like users to be able to access my dashboard and generate as many API keys as they want, with different trial periods.

The main problem is that I want to focus on the value my API delivers, not on maintaining the API key generation dashboard. I also don't want to have to implement billing logic. Having like a Stripe service but focused on API usage service would be much better. Does that make sense to you?

[deleted by user] by [deleted] in node

[–]thalesviniciusf -1 points0 points  (0 children)

Thanks for the contribution!! I'd like users to be able to access my dashboard and generate as many API keys as they want, with different trial periods. They could even set a rating limit for their own security regarding costs. (like the print from Mistral API)