Submit requests through Postman
When you’re testing endpoints with different parameters, you can use one of the many GUI REST clients available to make the requests. (By “GUI,” I mean there’s a graphical user interface with boxes and buttons for you to click.) You can also use curl (which we’ll cover soon), but GUI clients tend to simplify testing with REST APIs.
- Why use a GUI client
- Popular GUI clients
- Activity: Make requests with Postman
- Same request but in Paw instead of Postman
- Enter several requests for the Aeris API into Postman
- Automatically import the Postman collections
Why use a GUI client
With a GUI REST client, you can:
- Save your requests (and numerous variations) in a way that’s easy to run again
- More easily enter information in the right format
- See the response in a prettified JSON view or a raw format
- Easily include header information
With a GUI REST client, you won’t have to worry about getting curl syntax right and analyzing requests and responses from the command line.
Popular GUI clients
Some popular GUI clients include the following:
Of the various GUI clients available, Postman is probably the best option, since it allows you to save both calls and responses, is free, works on both Mac and PC, and is easy to configure.
A lot of times, abstract concepts don’t make sense until you can contextualize them with an action. In this course, I’m following more of an “experience-first” methodology. After you do an activity, we’ll explore the concepts in more depth. So if it seems like I’m glossing over concepts now, such as what a GET method is or an endpoint, hang in there. When we deep dive into these points in Documenting API endpoints, these concepts will be a lot clearer.
Activity: Make requests with Postman
Make a request
In this exercise, you’ll use Postman to make a request using OpenWeatherMap’s current weather data API endpoint. To make the request:
- If you haven’t already done so, download and install the Postman app at http://www.getpostman.com.
- Start the Postman app.
- If necessary, select GET for the method. (This is the default.)
- Insert the following endpoint into the box next to GET:
Click the Params tab (below the box where you inserted the endpoint) and then add the following three parameters in the key and value rows:
appidvalues with your own zip code and API key.
Your Postman UI should look like this:
When you add these parameters, they appear as a query string to the endpoint URL in the GET box. For example, your endpoint will now look like this:
https://api.openweathermap.org/data/2.5/weather?zip=95050&units=imperial&appid=fd4698c940c6d1da602a70ac34f0b147(but with different query string values). Query string parameters appear after the question mark
?symbol and are separated ampersands
&. The order of query string parameters doesn’t matter.
Many APIs pass the API key in the header rather than as a query string parameter in the request URL. (If that were the case, you would click the Headers tab and insert the required key-value pairs in the header.)
The response appears in the lower pane. For example:
Save the request
- In Postman, click the Save button (next to Send).
- In the Save Request dialog box, in the Request Name box at the top, type a friendly name for the request, such as “OpenWeatherMap Current API.”
- In the Request description (Optional) field, type a description such as “gets the current weather for 95050 in imperial units.”
Scroll down a bit and click Create collection to create a folder to save the request in (e.g., “OpenWeatherMap”). Then select the new collection you just created.
After you create the collection, the Save button will be enabled. Your Postman collection should look something like this:
- Click Save to [collection name]
Saved endpoints appear in the left side pane under Collections. (If you don’t see the Collections pane, click the Show/Hide Sidebar button in the lower-left corner to expand it.
Make a request for the OpenWeatherMap 5 day forecast
Now instead of getting the current weather, let’s use another OpenWeatherMap endpoint to get the forecast. Enter details into Postman for the 5 day forecast request. In Postman, you can click a new tab, or click the arrow next to Save and choose Save As. Then choose your collection and request name.
A sample endpoint for the 5 day forecast, which specifies location by zip code, looks like this:
Add in the query parameters for the API key and units:
(In the above code, replace out
APIKEY with your own API key.)
Make one more OpenWeatherMap API request
Make one more OpenWeatherMap API request, this time changing the parameters you’re using to specify the location (for either endpoint). For example, if you specified the location by zip code, change it to
lon geocoordinates instead. For example:
Same request but in Paw instead of Postman
Although Postman is a popular REST client, you can also use others, such as Paw. The following image shows the same current weather API request made in Paw (for Mac):
Like Postman, Paw also allows you to easily see the request headers, response headers, URL parameters, and other data. I like that Paw shows the response in an expandable/collapsible way. The expand/collapse feature can make it easier to explore the response. Note that Paw is specific to Mac only, and like most products for Mac users, costs money.
Enter several requests for the Aeris API into Postman
Now let’s switch APIs a bit and see some weather information from the Aeris Weather API, which you explored a bit in Scenarios for using a weather API. Constructing the endpoints for the Aeris Weather API is a bit more complicated since there are many different queries, filters, and other parameters you can use to configure the endpoint.
Here are a few pre-configured requests to configure for Aeris. You can paste the requests directly into the URL request box in Postman (after customizing the
CLIENTSECRET values), and the parameters will auto-populate in the parameter fields.
As with the OpenWeather Map API, the Aeris API doesn’t use a Header field to pass the API keys — the key and secret are passed directly in the request URL as part of the query string.
When you make the following requests, insert your own values for the
CLIENTSECRET (assuming you retrieved them in Get the authorization keys). If you don’t have a client ID or secret, you can use my keys here.
Get the weather forecast for your area using the observations endpoint:
Get the weather from a city on the equator — Chimborazo, Ecuador using the same observations endpoint:
Find out if all the country music in Knoxville, Tennessee is giving people migraines using the indices endpoint:
You’re thinking of moving to Arizona, but you want to find a place that’s cool. Use the normals endpoint:
With both the OpenWeatherMap and Aeris Weather API, you can also make these requests by simply going to the URL in your address bar (because the APIs are passed in the query string rather than the header). If so, use the JSON Formatter extension for Chrome to automatically format the JSON response in the browser view.
By looking at these two different weather APIs, you can see some differences in the way the information is called and returned. However, fundamentally both APIs have endpoints that you can configure with parameters. When you make requests with the endpoints, you get responses that contain information, often in JSON format. This is the core of how REST APIs work — you send a request and get a response.
Automatically import the Postman collections
Postman has a nifty import feature that will automatically pull in the same requests you’ve been entering. You can click the Run in Postman buttons below to automatically import these two collections into your own instance of Postman.
OpenWeatherMap API collection
If this button doesn’t work for you, copy this import link.
Aeris Weather API collection
If this button doesn’t work for you, copy this import link.
Clicking the Run in Postman buttons should automatically prompt you to import the collections into Postman. If it doesn’t work, copy the import link address and, in Postman, click Import in the upper-left corner. Then click the Import From Link tab, paste in the address and click Import.
If you’d like to learn more about Postman, listen to this interview with the Postman founder. We recorded this as part of the Write the Docs podcast and focused on the documentation features within Postman. For more information on creating the Run in Postman buttons, see the Run in Postman button section in the Getting started tutorial.
15/117 pages complete. Only 102 more pages to go.
Want to buy me lunch? Click the Donate button below to donate $10 through Paypal.