Welcome back! In the previous lessons, you learned how to set up a backend for a music player app, serve track data, and log when a user listens to a track. Now, let’s take the next step: accessing and displaying a user’s listening history.

Showing users their listening history is a key feature in most music apps. It helps users remember what they have listened to, discover patterns in their listening habits, and even get personalized recommendations. In this lesson, you will learn how to retrieve and display this history using the data we have been collecting.

Before we dive in, let’s quickly remind ourselves of the app’s structure and the data files involved. You have already set up:

• A tracks.json file that stores information about all available tracks.
• A sessions.csv file that logs each time a user listens to a track.

Here’s a quick look at how these are loaded and used in the app:

This code shows how we use Pandas to read both the track and session data. We will use these dataframes to find and display a user’s listening history.

Whenever a user listens to a track, we log that session in the sessions.csv file. Each row in this file represents one listening event and contains the following columns:

To get a specific user’s listening history, we need to filter this file for their user_id. Here’s how this is done in the code:

Explanation:

• The function checks if the sessions file exists.
• It loads the sessions into a DataFrame.
• It filters the DataFrame to include only rows where user_id matches the given user.
• If anything goes wrong, it returns an empty DataFrame.

Example Output:
If you call get_user_listening_history("1"), you might get:

To make this listening history available to the frontend or other services, we expose it through an API endpoint. Here’s the relevant part of the code:

Explanation:

• The endpoint /api/history/<user_id> accepts a user ID as part of the URL.
• It calls the get_user_listening_history function to get the user’s sessions.
• The result is converted to a list of dictionaries (one per session).
• The API returns a JSON object with the user ID and their listening history.

Sample API Response:

This makes it easy for any client (like a web or mobile app) to display the user’s listening history.

Right now, your listening history only shows user ID, track ID, and timestamps. But wouldn’t it be more useful to also show track info — like title, artist, and genre?

Let’s upgrade your API to include full metadata. Here’s how it works:

This version merges the listening logs with the full track list from tracks.json.

In the app.py, add this new route:

Now a request to curl -s http://localhost:5001/api/history/user123/detailed might return:

This is what powers the "Recently Played" screens you see in real music apps.

In this lesson, you learned how to access and display a user’s listening history by:

• Filtering session data for a specific user.
• Returning the results through a dedicated API endpoint.

This is a key feature for any music app, helping users keep track of what they have listened to. You are now ready to practice these skills and build on what you have learned.

Congratulations on reaching the end of this course! You have built a solid foundation for handling music data and session tracking. Keep experimenting and applying these concepts to your own projects!