Software as a Service

40 readers

1 users here now

Software As a Service Companies — The Future Of Tech Businesses Discussions and useful links for SaaS owners, online business owners, and more.

founded 2 weeks ago

MODERATORS

Carl@programming.dev

Is it a good idea to build out a no-code platform for an API (programming.dev)

submitted 2 weeks ago by Carl@programming.dev to c/saas@programming.dev

6 comments fedilink hide all child comments

I currently have an API that is gaining traction. I would like to market towards people that are able to use APIs, however there is a technical barrier when It comes to requesting an endpoint, saving data, building a script around that, etc.

Should I build a web application that allows non-technical users to access the data from the API? Or, Is that a waste of time for the effort put in?

you are viewing a single comment's thread
view the rest of the comments

[–] RonSijm@programming.dev 7 points 2 weeks ago (1 children)

It's a bit of a vague question, generally an API is backend - and you're kinda asking "should I make a frontend for this?" - hard to tell without context...

If you just want a "semi-developer-ish" frontend, you could look into just making an OpenAPI spec for it, and using something like Swagger as a frontend. Then at least you have some kind of GUI

[–] Carl@programming.dev 1 points 1 week ago

Currently I have a documentation page that points users to the endpoints. I also have the fastapi OpenAPI documentation available for users.

For what im doing it will be a mixture of what OpenAPI does with the requests directly in the documentation and the ability to create "bots" around it for non-technical users like airtable.