Creating A NASA API Postman Collection And Environment

This is a story derived from work to help develop a Postman Collection that could be used by the International Space Apps Challenge, establishing a machine readable definition for all the NASA APIs available at that can be used by participations in the challenge, helping developers quickly get up to speed with the valuable APIs NASA provides. The International Space Apps Challenge is in need of sponsors and participants to help make the event a success--please visit, or on Twitter at @SpaceApps to get involved.

I met Katelyn Hertel (@Katers_Potaters) from the International Space Apps Challenge at POSTCON, and we got to talking about the interesting APIs NASA has, and how we can use Postman to make things easier for the developers who are participating in the global challenge. I immediately knew what was needed, and as soon as I got home this weekend I got to work on crafting a Postman Collection for all of the NASA APIs. It took me about four hours t apply for a key, and get up and running with each of the NASA APIs using Postman. As I was playing around with each of the individual API resources, which come from across many different groups, I took the liberty to better organize them, and came up with the following sub-folders for the NASA API Postman collection.

I could spend days writing better summaries, descriptions, and organizing APIs into more meaningful folders and requests, but this should provide a good starting point. All 79 of the individual API requests work, allowing me to easily generate examples and documentation when ready. Here is the current draft of the NASA API Postman Collection. I thought about breaking it into separate collections, one for reach area, but I thought it worked better as one collection, abstracting away the different APIs that come from different groups. I did manage to standardize some of the parameters across the APIs using a Postman Environment, helping potentially reduce some friction running the different APIs. There is still much more work to be done across the APIs to help clean up some of the design and documentation available, but it provides a pretty robust picture of the different APIs NASA offers.

This NASA API Postman Collection should help reduce friction for developers at the International Space Apps Challenge, providing them with a quick way to get up and running with any of the NASA APIs. Each developer will still need to signup for their own API key, but once they save their key as part of their Postman Environment, they should be able to use any of the 79 API requests organized within the collection. I’m going to work with the International Space Apps Challenge folks to polish the collection a bit, and publish as part of the resources on the website for the challenge. Along the way I’ve learned a lot of NASA’s APIs, and organizing resources as a Postman Collection, something I will be talking about in ongoing stories here on the blog, showcasing how I profiled NASA APIs using Postman.