- Python Automation Cookbook
- Jaime Buelta
- 99字
- 2021-06-30 14:52:57
Accessing web APIs
Rich interfaces can be created through the web, allowing powerful interactions through HTTP. The most common interface is through RESTful APIs using JSON. These text-based interfaces are easy to understand and to program, and use common technologies that are language agnostic, meaning they can be accessed in any programming language that has an HTTP client
module, including, of course, Python.
Formats other than JSON are used, such as XML. But JSON is a very simple and readable format that translates very well into Python dictionaries (and other language equivalents). JSON is, by far, the most common format in RESTful APIs at the moment. Learn more about JSON here: https://www.json.org/.
The strict definition of RESTful requires some specific characteristics, but an informal definition of RESTful is a system that describes resources through HTTP URLs. This means each URL represents a particular resource, such as an article in a newspaper or a property on a real estate site. Resources can then be manipulated through HTTP methods (GET
to view, POST
to create, PUT
/PATCH
to edit, and DELETE
to delete).
Proper RESTful interfaces need to have certain characteristics. They are a way of creating interfaces that is not strictly restricted to HTTP interfaces. You can read more about it here: https://codewords.recurse.com/issues/five/what-restful-actually-means.
Using requests
is very easy with RESTful interfaces, as they include native JSON support.
Getting ready
To demonstrate how to operate RESTful APIs, we'll use the example site https://jsonplaceholder.typicode.com/. It simulates a common case with posts, comments, and other common resources. We will use posts and comments. The URLs to use will be as follows:
# The collection of all posts
/posts
# A single post. X is the ID of the post
/posts/X
# The comments of post X
/posts/X/comments
The site returns the correct result for each of them. Pretty handy!
Because it is a test site, data won't be created, but the site will return all the correct responses.
How to do it...
- Import
requests
:>>> import requests
- Get a list of all posts and display the latest post:
>>> result = requests.get('https://jsonplaceholder.typicode.com/posts') >>> result <Response [200]> >>> result.json() # List of 100 posts NOT DISPLAYED HERE >>> result.json()[-1] {'userId': 10, 'id': 100, 'title': 'at nam consequatur ea labore ea harum', 'body': 'cupiditate quo est a modi nesciunt soluta\nipsa voluptas error itaque dicta in\nautem qui minus magnam et distinctio eum\naccusamus ratione error aut'}
- Create a new post. See the URL of the newly created resource. The call also returns the resource:
>>> new_post = {'userId': 10, 'title': 'a title', 'body': 'something something'} >>> result = requests.post('https://jsonplaceholder.typicode.com/posts', json=new_post) >>> result <Response [201]> >>> result.json() {'userId': 10, 'title': 'a title', 'body': 'something something', 'id': 101} >>> result.headers['Location'] 'http://jsonplaceholder.typicode.com/posts/101'
Notice that the
POST
request to create the resource returns201
, which is the proper status for created. - Fetch an existing post with
GET
:>>> result = requests.get('https://jsonplaceholder.typicode.com/posts/2') >>> result <Response [200]> >>> result.json() {'userId': 1, 'id': 2, 'title': 'qui est esse', 'body': 'est rerum tempore vitae\nsequi sint nihil reprehenderit dolor beatae ea dolores neque\nfugiat blanditiis voluptate porro vel nihil molestiae ut reiciendis\nqui aperiam non debitis possimus qui neque nisi nulla'}
- Use
PATCH
to update its values. Check the returned resource:>>> update = {'body': 'new body'} >>> result = requests.patch('https://jsonplaceholder.typicode.com/posts/2', json=update) >>> result <Response [200]> >>> result.json() {'userId': 1, 'id': 2, 'title': 'qui est esse', 'body': 'new body'}
How it works...
Two kinds of resources are typically accessed – single resources (https://jsonplaceholder.typicode.com/posts/X
) and collections (https://jsonplaceholder.typicode.com/posts)
- Collections accept
GET
to retrieve all the members of the collection andPOST
to create a new resource - Single elements accept
GET
to get the element,PUT
andPATCH
to edit, andDELETE
to remove elements
All the available HTTP methods can be called in requests. In the previous recipes, we used .get()
, but .post()
, .patch()
, .put()
, and .delete()
are available.
The returned response object has a .json()
method that decodes the result from JSON.
Equally, to send information, a json
argument is available. This encodes a dictionary into JSON and sends it to the server. The data needs to follow the format of the resource or an error may be raised.
GET
and DELETE
don't require data, while PATCH
, PUT
, and POST
do require data to be sent through the body payload.
The referred-to resource will be returned, and its URL is available in the header. This is useful when creating a new resource, as its URL is not known beforehand.
The difference between PATCH
and PUT
is that the latter replaces the whole resource, while the former does a partial update.
There's more...
RESTful APIs are very powerful but also have huge variability. Please check the documentation of the specific API to learn about its details.
See also
- The Downloading web pages recipe, earlier in this chapter, to learn the basics of requesting web pages
- The Installing third-party packages recipe in Chapter 1, Let's Begin Our Automation Journey, to learn the basics of installing external modules