# Generating Request URLs¶

In a REST API, the client or application program– the kind of program you will be writing– makes an HTTP request that includes information about what kind of request it is making. Web sites are free to define whatever format they want for how the request should be formatted. This chapter covers a particularly common and particularly simple format, where the request information is encoded right in the URL. This is convenient, because if something goes wrong, we can debug by copying the URL into a browser and see what happens when it tries to visit that URL.

In this format, the URL has a standard structure:

• the base URL
• a ? character
• one or more key-value pairs, formatted as key=value pairs and separated by the & character.

For example, consider the URL http://services.faa.gov/airport/status/DTW?format=json. Try copying that URL into a browser. It returns data about the current status of the Detroit airport. This web service is provided by the FAA, the Federal Aviation Administration.

Let’s pull apart that URL. In this case, the FAA uses a slight variation on the basic structure described above.

• the base URL is http://services.faa.gov/airport/status/
• after status/, there is a three letter code representing the airport, in this case DTW
• a ? character
• key=value pairs. In this case, there is exactly one pair. The key is format and the value is json, yielding the text string format=json.

All those parts are concatenated together to form the full URL. If you substitute LGA for DTW, you will get the current conditions at New York’s LaGuardia airport instead.

## Encoding URL Parameters¶

Here’s another URL that has a similar format. https://www.google.com/search?q=%22violins+and+guitars%22&tbm=isch. It’s a search on Google for images that match the string “violins and guitars”. It’s not actually based on a REST API, because the contents that come back are meant to be displayed in a browser. But the URL has the same structure we have been exploring above and introduces the idea of “encoding” URL parameters.

• The base URL is https://www.google.com/search

• ?

• Two key=value parameters, separated by &
• q=%22violins+and+guitars%22 says that the query to search for is “violins and guitars”.
• tbm=isch says to go to the tab for image search

Now why is "violins and guitars" represented in the URL as %22violins+and+guitars%22? The answer is that some characters are not safe to include, as is, in URLs. For example, a URL path is not allowed to include the double-quote character. It also can’t include a : or / or a space. Whenever we want to include one of those characters in a URL, we have to encode them with other characters. A space is encoded as +. " is encoded as %22. : would be encoded as %3A. And so on.

## Using requests.get to encode URL parameters¶

Fortunately, when you want to pass information as a URL parameter value, you don’t have to remember all the substitutions that are required to encode special characters. Instead, that capability is built into the requests module.

The get function in the requests module takes an optional parameter called params. If a value is specified for that parameter, it should be a dictionary. The keys and values in that dictionary are used to append something to the URL that is requested from the remote site.

For example, in the following, the base url is https://google.com/search. A dictionary with two parameters is passed. Thus, the whole url is that base url, plus a question mark, ”?”, plus a “q=...” and a “tbm=...” separated by an “&”. In other words, the final url that is visited is https://www.google.com/search?q=%22violins+and+guitars%22&tbm=isch. Actually, because dictionary keys are unordered in python, the final url might sometimes have the encoded key-value pairs in the other order: https://www.google.com/search?tbm=isch&q=%22violins+and+guitars%22. Fortunately, most websites that accept URL parameters in this form will accept the key-value pairs in any order.

d = {'q': 'violins and guitars', 'tbm': 'isch'}
print results.url


prediction-23: How would you request the URL http://bar.com/goodstuff?greet=hi+there&frosted=no using the requests module?