# Testing REST API

Nowadays it’s hard to find a web-application, which doesn’t use REST API. That’s an essential part of application functionality that we have to test. Usually REST API calls are covered with integration tests. However, if by some reason, it isn’t done you can still test it with Puppetry.

Let’s put it into practice. Imagine we have a marketplace application, which relies on [Magento API](https://devdocs.magento.com/swagger/index.html).

To start, we check if product information can be retrieved. So we use `page.assertRest` as follows:

![Making GET request and asserting the response](https://3461068122-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LdyKJ-zzeS2hB7DF04J%2F-LvBuiCThnDiQBbTnZev%2F-Lvtv4zUq90kERtqX34a%2Fassert-rest-get.png?alt=media\&token=5a5b86f6-824e-4e43-ab23-d8fbeadb8c45)

Here we assert that call respond with status code 200 (success) and the returned JSON matches the given [JSONPath](https://www.npmjs.com/package/jsonpath).

Now let’s do something more sophisticated. We are going to obtain authentication token.

The application calls `integration/admin/token` to obtain authentication token. So we set `page.assertRest` parameters like that:

![Making POST request and asserting the response](https://3461068122-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LdyKJ-zzeS2hB7DF04J%2F-LvBuiCThnDiQBbTnZev%2F-LvtvG2N3zl6HDEM4VFk%2Fassert-rest-post.png?alt=media\&token=dbeb9e36-01a9-4858-82d3-b4d89d02ddb9)

We expect the response of status 200 with a non-empty access token.

Note that `page.assertRest` automatically assigns the response text to `PUPPETRY_LAST_RESPONSE_TEXT` template variable. So we can use it further in the test case.