The other day I was building a Python script to fetch some information about all my repositories on GitHub. Their API is pretty straightforward and well documented.

Fetching my repos was as simple as:

>>> import requests
>>> response = requests.get("")

The thing is that such request gave me a list with all my repos on it. No info on pagination whatsoever on the response body. After a bit of research, I found out that GitHub APIs take advantage of the Link header to expose several pagination options. Given that I hadn’t seen such a header before, I went ahead and inspected it:

>>> response.headers["link"]
'<>; rel="next", <>; rel="last"'

Cool! It’s not just giving me a link to the next page, but also to the last one. Nice!

But wait, that’s a string! What am I supposed to do with that? Write a small parser to extract such headers? Shouldn’t be hard to do so, but there must be a better way.

Of course there is! The awesome requests library never let me down and this time was no exception. It parses such headers and exposes the pagination info via the Response.links attribute:

>>> response.links
  'next': {
    'url': '',
    'rel': 'next'
  'last': {
    'url': '',
    'rel': 'last'
>>> response.links["next"]
{'url': '', 'rel': 'next'}
>>> response.links["last"]
{'url': '', 'rel': 'last'}

Simple like that. 🙂

If you want to learn more about this standard, check out the IETF’s RFC8288.