Posted on 07-10-2014
I want the Federal Executive Agency Domain API from the GSA to be included in the APIs.io search engine. To do this, I need to create an APIs.json file, and host it in the root of the explore.data.gov domain--which I do not have access to. ;-(
While I cannot put an APIs.json in the root of the expore.data.gov domain, I can create one, and host it myself. So I created this Github repository, to act as a holder for the explore.data.gov domain. I will be putting everything that "should be available" in the Federal Executive Agency Domain API from the GSA.
An APIs.json is meant to act as an index of APIs available at the explore.data.gov domain, the Federal Executive Agency Domain API is just the first one I'm tackling. For the explore.data.gov/apis.json to be effective, it needs a machine readable API definition for the Federal Executive Agency Domain API to point to. While the API is simple and well designed, it currently doesn't have a machine readable API definition--I am going to fix that.
I have created a Swagger API definition for the Federal Executive Agency Domain API, describing the interface using JSON. Now I have a machine readable definition of this API. Now I can list the API, in my APIs.json for the explore.data.gov domain--which I will talk abut in my next post.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|