API Discovery: Can we do better?
blog.apis.guru
API Discovery: Can we do better?
1–10 of 47 posts
Re: API Discovery: Can we do better?
#2Re: API Discovery: Can we do better?
#3Semi-related question: is there a list of things that actually use Schema.org, outside of Google Search for some things?
Re: API Discovery: Can we do better?
#4I now have wrapped a couple of API's in swagger and using swagger-ui to create beautiful interactive api docs for users.
Moving forward I'm going to wrap most of our legacy systems around a swagger spec'ed API and discontinue any alternative access to these systems as time goes by.
Re: API Discovery: Can we do better?
#5I wonder if the author knows about Swagger specs; They also started the OpenAPI initiative[0]. I now have wrapped a couple of API's in swagger and using swagger-ui to create beautiful interactive api docs for users. Moving forward I'm going to wrap most of our legacy systems around a swagger spec'ed API and discontinue any alternative access to these systems as time goes by. [0]: http://swagger.io/introducing-the-ope…
I'm the author, and I definitely know about Swagger/OpenAPI. By coincidence, I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory
But I have learned the hard truth over last two years: API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this.
P.S. it is pretty easy to generate Schema.org type based on Swagger/OpenAPI spec.
Re: API Discovery: Can we do better?
#6I wonder if the author knows about Swagger specs; They also started the OpenAPI initiative[0]. I now have wrapped a couple of API's in swagger and using swagger-ui to create beautiful interactive api docs for users. Moving forward I'm going to wrap most of our legacy systems around a swagger spec'ed API and discontinue any alternative access to these systems as time goes by. [0]: http://swagger.io/introducing-the-ope…
Hi, I'm the author, and I definitely know about Swagger/OpenAPI. By coincidence, I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory But I have learned the hard truth over last two years: API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this. P.S. it is pretty easy to generate Schema.org type based on Swagger/OpenAPI sp…
Re: API Discovery: Can we do better?
#7Earlier quoted context omitted.
Hi, I'm the author, and I definitely know about Swagger/OpenAPI. By coincidence, I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory But I have learned the hard truth over last two years: API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this. P.S. it is pretty easy to generate Schema.org type based on Swagger/OpenAPI sp…
Would you mind to share a link for that? I am very interested as I work on different projects with swagger apis.
And here is github repo: https://github.com/APIs-guru/openapi-directory
Re: API Discovery: Can we do better?
#8I wonder if the author knows about Swagger specs; They also started the OpenAPI initiative[0]. I now have wrapped a couple of API's in swagger and using swagger-ui to create beautiful interactive api docs for users. Moving forward I'm going to wrap most of our legacy systems around a swagger spec'ed API and discontinue any alternative access to these systems as time goes by. [0]: http://swagger.io/introducing-the-ope…
Hi, I'm the author, and I definitely know about Swagger/OpenAPI. By coincidence, I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory But I have learned the hard truth over last two years: API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this. P.S. it is pretty easy to generate Schema.org type based on Swagger/OpenAPI sp…
Ah cool, thanks for the link and effort. Will have a look at it as time allow.
> It is pretty easy to generate Schema.org type based on Swagger/OpenAPI spec.
Do you have any example or gist of a snipped of code to accomplish this?
> API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this.
But does the API catalog not enable auto discovery? Agreeing you maintaining a list is not scalable.
Re: API Discovery: Can we do better?
#9Re: API Discovery: Can we do better?
#10Earlier quoted context omitted.
Hi, I'm the author, and I definitely know about Swagger/OpenAPI. By coincidence, I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory But I have learned the hard truth over last two years: API catalogs aren't scalable solutions for API discovery. That's why I'm pushing this. P.S. it is pretty easy to generate Schema.org type based on Swagger/OpenAPI sp…
> I'm maintainer of the collection of 250+ Swagger specs for public APIs: https://github.com/APIs-guru/openapi-directory Ah cool, thanks for the link and effort. Will have a look at it as time allow. > It is pretty easy to generate Schema.org type based on Swagger/OpenAPI spec. Do you have any example or gist of a snipped of code to accomplish this? > API catalogs aren't scalable solutions for API discovery. That's w…