Live data from Hacker News

Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

apirank.dev

41–50 of 62 posts

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#41

I think this sort of resource (if including actual use-cases and potential alternatives) could be useful. Right now it shows scores for security, performance, reliability, design, popularity, and those seem to be calculated with very loose and unreliable scoring and I'm guessing they are mostly there to fill out the content. There does not seem to be non-openapi api:s there (for example OSM, wikipedia or any IA) I do…

I agree that there is a lot of room for improvement. We are a small team and we had to start somewhere to have feedback from the community and improve accordingly :)

Thanks for the great ideas, I share your opinion on those

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#43

This seems to lack tons of APIs , maybe instead of 'apirank' it should be called 'openapi dev rank'. Apple Itunes : https://developer.apple.com/library/archive/documentation/Au... last fm : https://www.last.fm/api acoustid : https://acoustid.org/webservice spotify : https://developer.spotify.com/documentation/web-api/ discogs : https://www.discogs.com/developers deezer : https://developers.deezer.com/login?redirect=/…

Spotify is there (twice!): https://apirank.dev/Spotify-Web-API/ https://apirank.dev/Spotify/ The search appears to be broken, because it returns no results for spotify.

[deleted]

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#44
post #32
post #20

Earlier quoted context omitted.

or the two most famous ones I know of: * https://boto3.amazonaws.com/v1/documentation/api/latest/refe... * e.g. https://cloud.google.com/iam/docs/reference/rest I'm sure there's an Azure one, too, I just don't currently play in that sandbox I know that DataDog also uses openapi but since this site's search it broken, hard to know if it's hiding on page 57 or what

We used Algolia free tier for the search but all the credits were consumed :') I take this as a learning for our next side project

I try to impress upon my colleagues that error handling is the hallmark of good engineering, because the happy path is only one possible outcome

Had the search said "error while searching: 403" (or whatever) versus "no results" there would have been far fewer complaints in this thread

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#46
post #38
post #29

The performance metric is meaningless. As you yourself acknowledge, this is way too dependent on underlying business logic to be able to compare objectively. A 100ms API response may as well be "slower" than a 500ms one depending on what the calls are actually achieving. Say service A has an API: - GET /users/ - 100ms Service B has multiple APIs: - GET /users/ - 100ms - GET /users - 250ms - GET / - 500ms Which servic…

This is an experimental research we did mostly because we thought it was cool and new. There are limitations indeed, though if you compare similar APIs with similar business intent, their structure should also have similarity, unlike your example. For the popularity metrics, I will take a look - I admit we can do better :)

What's the methodology? It's an interesting metric as long as there is some rationale attached.

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#48
"Ranking" normally implies decisive weight: we rank related things in order to decide between them. I'm not sure how I'm supposed to decide between "P J S Paul Ministries" and the Coindesk API, which are currently #1 and #2 respectively.

Similarly: how can you meaningfully measure the performance, security, or reliability of these APIs without first determining whether you're communicating meaningfully with them? I assume that many (most?) of these APIs require some kind of credential; it's hard to glean anything of interest from a server's ability to reliably send an error message,

Re: Show HN: APIRank.dev – We crawled and ranked public APIs from the internet

#49
post #6

A terribly designed API with a complete and orderly OpenAPI 3.0.0 spec will get 5/5. A well designed API with no OpenAPI support or 3.1.x spec support will get a poor design score. I think user generated content might be the way to go for Design. Let people score and review the design quality.

I would suggest renaming the Design category to Documentation. Design is subjective, so user generated content might be an option, but ultimately docs and examples as (non subjective) a measure are probably more useful to most developers.
Post reply on HN