11–20 of 62 posts
This sounds silly, but I'm honestly curious: do you offer this information as an API? On a more serious note, if the purpose is to be able to compare candidate APIs that you're looking at using, here are some features that I think might be helpful: * Tagging, and filtering based on those tags. Example: "Show me APIs that deal with SMS" * Select two or more APIs for direct comparison. Example: "Compare Twilio, CleverT…
would be nice if it explains why OpenAPI 3.0.0-compliance (with comments, examples, etc.) matters.
I run a SaaS that helps people get API data into Google Sheets.
For very popular services, we make customized connectors that hide all the complexity.
For medium popularity services, we do some automated transforms to hide complexity in the requests, and massage the response shape to an easier-to-consume format.
For low popularity services, we'll do a best-effort to point customers towards docs and common pitfalls.
All of that is to say: I've seen a lot of APIs!
So it's very bizarre to see Xero ranked #3 out of 5,651. Xero has this convoluted system where you need to query to get your tenant ID, and then pass that as a header. If you don't pass it, you get an opaque error message. That's the 3rd best API, eh?
Also, you sort of have to wonder how much human review went into this. GitHub has an OpenAPI spec, is a hugely popular service, and seems to be absent from this index.
(edit: Perhaps Github is present? I got no results when I searched "github", but I also get no results if I search "xero", despite Xero Assets API being the 3rd hit.)
Whats the difference between this and simply Googling for api?
Hey, co-author here! Google does not allow you to browse APIs according to Security, Reliability, not Performance, etc. Google is not an OpenAPI spec indexer either ;)
And most of them have status pages that let me know their reliability.
would be nice if it explains why OpenAPI 3.0.0-compliance (with comments, examples, etc.) matters.
Yes! I assume that this is just content marketing to get link juice to feed our Google overlords, but yeesh. I run a SaaS that helps people get API data into Google Sheets. For very popular services, we make customized connectors that hide all the complexity. For medium popularity services, we do some automated transforms to hide complexity in the requests, and massage the response shape to an easier-to-consume forma…
Is the plan to actually build this out to be a usable tool or is it just a way for you to get people to submit API:s and get some marketing?
Earlier quoted context omitted.
Yes! I assume that this is just content marketing to get link juice to feed our Google overlords, but yeesh. I run a SaaS that helps people get API data into Google Sheets. For very popular services, we make customized connectors that hide all the complexity. For medium popularity services, we do some automated transforms to hide complexity in the requests, and massage the response shape to an easier-to-consume forma…
What SaaS is it? I think I have a feel for exactly this
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=/api
music brainz : https://musicbrainz.org/doc/MusicBrainz_API
gracenote : https://developer.tmsapi.com/Sample_Code
---
Additionally, why not list API rate limits?
Or some lookups don't need any security, like querying Apple Itunes does not require anything except for being nice and rate limiting.
A sample response takes this form: `{ type: 'data', nodes: [ { type: 'data', data: [Array], uses: [Object] }, ... ] }`
Things get a little strange (for me at least!) when I start poking around in the data array. At index 0 in this array is an object with some information on what I think is mostly just paging and the length of the data array (sans this first element). At index 1 is an array filled with numbers that correspond to array indices in the initial data array, and the objects at those specified indices are the actual data sources. While the keys in those objects are actual descriptors of relevant information, the VALUES for those keys are also array indices. Essentially the incoming data structure is a super flattened array with some objects/ additional arrays that just point to other indices in the data array.[1]
Is there a name for this type of pattern? Is it just an artifact of using some query library to handle data fetching? Apologies for the naivety, I still consider myself a fairly new dev (especially when I see something like this!).
[1] More complete example (not sure if I explained this well):
{
type: 'data',
data: [
{ endpoints: 1, count: 3971, currentPage: 5 },
[2,221,355,...], // at array index 2 we should expect an object
{ id: 3, commentsRatio: 4, owaspIssues: 6, ... }, // array index 2: object with values that are all indices in the original data array that hold the actual values!
...
]
}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=/…
* 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