Posted on 07-10-2014
After creating a machine readable API definition using Swagger for explore.data.gov, I now want to nwo create an APIs.json file, which will act as directory of the APIs available at explore.data.gov.
Of course, this isn't the real domain, but if the GSA wants, they can take the APIs.json, and any API definitions, and migrate to their own servers That is one of the goals of this project:
- Play with the APIs.json format
- Make GSA APIs available to APIs.io
- Get the attention of GSA so they will a) Copy APIs.json b)Copy the Swagger API definitions, and publish them both at explore.data.gov (then keep up to date)
With that in mind, I've now published a machine readable APIs.json file, which provides an index of the APIs I've created definitions for in Swagger.
When APIs.io is updated to support 0.14 of the APIs.json format, I will submit this APIs.json for indexing. My entry won't register as authoratative, because the APIs.json isn't actually within the explore.data.gov domain. However the APIs I have published here will get indexed, and made available in the API search engine.
I only have the Federal Executive Agency Internet Domains API published here currently, but maybe I'l find and publish others here in the future. Until then this project will remain as is.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|