Besides by doing market research, how can one find out what are API's that people are actually looking for and willing to pay for?
What we where after and gave up on was an API that would accept an EAN-13 barcode and return product details, images, good descriptions, in multiple language (specifically NOT machine translated) and possible alternative EAN-13 barcodes for the same product.
As a side project to this: An API that will take a list of EAN-13 barcode, a price and a quantity (in stock) and transform it into a number of feeds for various price comparison sites. Again, it exists, but it's expensive, not all that good and it certainly doesn't automatically add product name, descriptions, categories and product attributes.
I think that issue here is, and it's almost bound be the same for most other APIs, it's the data that's interesting. So what data do you have access to that most others don't? My guess is that there aren't any large and interesting dataset that a random person on HN can easily sell, that isn't already readily available.
Third-party risk is the biggest problem with APIs. The amount of calls I've been in where a third-party provider tried to sell their API and told me they don't need versioning right now, they will "try to" pre-announce breaking changes, they don't have an SLA or uptime commitment, etc. etc. is way too many. It's so hard to find an API provider that seems to be trustworthy enough to build a product on top of it.
I feel like there's a magic number of salaried positions that need to be tied to an API provider, to ensure it's both dynamic enough to react to generational changes in networking/security/etc. but also slow enough to not keep throwing everything overboard whenever a new framework or middle-manager comes along.
However for my own personal accounts... just let me call the API!
Most successful API products in the sense that you're describing share two common characteristics:
1. They are a thin wrapper around some dynamic dataset.
2. The cost to an organization maintaining that dataset is prohibitively large and/or difficult relative to the value they receive from it.
If I were in your shoes, I'd find a niche that I was relatively well-positioned to address (say, Shopify stores, or programmatic SEO — something small enough to have a uniform opinion but large enough such that there are multiple cohorts of individuals willing to pay) and spend time in their forums looking for people complaining about datasets or information they wish they had. The API part is an implementation detail.
Does asking professionals directly what they're missing count as market research?
Does this post count as market research?
- Ask for all admin1 regions of a country and have all their actual data (like: all states in the US, or all regions in Italy)
- Ask for all admin2 regions in a given admin1 region (all counties in the state of TX, all provinces in the region of Lombardy). As you can already see "US.TX" is an identifier but "IT.Lombardy" is not, it is language dependent and I'm sure there are international identifiers for those but they are lacking in almost all geo something APIs
- Ask for all admin3 in some admin2
- Ask for all admin-whatever on a given ZIP code
- Ask for all ZIP codes in a given admin-something
- Bonus point if it supports i18n and l10n
If anyone knows of one please tell me, I would pay for it right now.
I think either catering to your own first need is better than trying to build a thing you might not understand well. The alternative is to just do a poll on a large channel of distribution like a nocode platform where they're dying for a certain dataset.
In general I might pay for APIs that correlate data from multiple sources into one endpoint.
As an European, with the current energy situation, I might pay for an API that combines weather data, electricity market prices and other factors into a single API that estimates electricity costs.
Or maybe an API that combines ratings from IMDB, Rotten Tomatoes, Metacritic, Letterboxd etc into one call.
https://github.com/samsquire/ideas4#5-permanent-softwareplat...
BSD sockets solved communication for everyone in one library that everyone uses. But communication isn't the only problem we have.
Most of the problems listed are solved independently by each software shop, installation and company.
This is a huge value add for my customers.
Most build an MVP product.
If you’re selling access to data, it’s niche and easily replaced.
A product with corporate and business integrations? Not so easy.
I've also had customers scared off or investors not want to invest because it is a plain API platform and not B2C...
To answer the question market research is kind of the only way to know, Google adwords keyword planner and Google trends are quite good, as well as researching the companies in the same space well and what gaps there APIs have.
As an example https://text-generator.io distinguishes itself from OpenAI by including automatic analysis for input links, linked images, documents etc and doing speech to text/self hosting/embedding images, text and code in the same space, so isn't just an API clone