this post was submitted on 05 Sep 2024
7 points (88.9% liked)

Software as a Service

42 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 1 month ago
MODERATORS
 

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
[โ€“] onlinepersona 3 points 1 month ago* (last edited 1 month ago)

Dunno what the API is like, but if you document it, generate an openapi yaml and provide an interface based upon that (your app framework probably supports it), it'll be easier for people to test with an API key or on a demo instance with a public API key.

Also you van build integrations for actual no code platforms like N8N or zapier. They might even be able to generate an integration for you from an OpenAPI spec.

Anti Commercial-AI license