Consuming APIs in Angular: Displaying Data In Components

Learn how to fetch a list of items from a REST API and display it in an Angular component.

Florimond Manca,

Welcome back! This article is a follow up to a previous article, Consuming APIs in Angular: The Model-Adapter Pattern. If you haven't read it yet β€” go check it out! This post will be referencing it quite often.

I had a question from a reader about how the CourseService could be used in a component, say, to display the list of courses. This is exactly what we'll cover in this beginner-friendly article.

This post should be helpful to anyone wondering how to retrieve and display data fetched from an external API. 😊

Quick refresher

In the original post, we discussed a design pattern that I use to standardise how my Angular apps communicate with REST APIs: the Model-Adapter pattern.

Given the GET /courses API endpoint, we built a Course model, a CourseAdapter and a CourseService that can help us fetch the list of courses from the API.

Here's what the project structure looks like for now:

β”œβ”€β”€ app.component.css
β”œβ”€β”€ app.component.html
β”œβ”€β”€ app.component.ts
β”œβ”€β”€ app.module.ts
└── core
    β”œβ”€β”€ course.model.ts
    └── course.service.ts

The goal here is to build a CourseListComponent that fetches the list of courses using the CourseService, and displays them in the form of a simple unordered list.

Let's build!

Generating the CourseListComponent

Okay, let's get started. First, we will generate the component using the Angular CLI:

ng generate component CourseList

The TypeScript (TS), HTML and CSS files for the component will be generated under src/app/course-list/. Here's what the TS file looks like so far:

// course-list/course-list.component.ts
import { Component, OnInit } from "@angular/core";

  selector: "app-course-list",
  templateUrl: "./course-list.component.html",
  styleUrls: ["./course-list.component.css"],
export class CourseListComponent implements OnInit {
  constructor() {}

  ngOnInit() {}

Setting up attributes and templates

As a first step, let's add an empty list of courses on the component:

  // course-list/course-list.component.ts
  import { Component, OnInit } from '@angular/core';

    selector: 'app-course-list',
    templateUrl: './course-list.component.html',
    styleUrls: ['./course-list.component.css']
  export class CourseListComponent implements OnInit {

+   courses: Courses[];

-   constructor() { }
+   constructor() {
+ = [];
+   }

    ngOnInit() {


Next, let's set up the template. Nothing fancy here, we're just using an *ngFor to display each course in its own list item, as well as the DatePipe to format the date.

<!-- course-list/course-list.component.html -->
  <li *ngFor="let course of courses">
      {{ }} β€’ {{ course.code }} β€’ Created {{ course.created | date

While we're at it, let's update the AppComponent's template to display the list of courses:

<!-- app.component.html -->


Alright! Let's fire up the browser, and we should be greeted with the "Courses" title and… an empty list. Why? Well, we haven't fetched any course yet!

Implementing the API endpoint

Before we go and plug the CourseService in, remember that for now it refers to β€” and that API doesn't exist!

That said, it would be nice to test the CourseService against a live server, wouldn't it?

So, let's build a quick backend API for this exact purpose. I'll be using Python and Starlette to provide the GET /courses endpoint we need to have access to from the browser.

You don't need to know about Python nor understand the code below, but I'm displaying it here for those interested:

# Install: `pip install starlette uvicorn`
import uvicorn
from starlette.applications import Starlette
from starlette.middleware import Middleware
from starlette.middleware.cors import CORSMiddleware
from starlette.responses import JSONResponse
from starlette.routing import Route

        "id": 1,
        "code": "adv-maths",
        "name": "Advanced Mathematics",
        "created": "2018-08-14T12:09:45",
        "id": 2,
        "code": "cs1",
        "name": "Computer Science I",
        "created": "2018-06-12T18:34:16",

async def courses_list(request):
    return JSONResponse(COURSES)

routes = [
    Route("/courses", courses_list),

middleware = [

app = Starlette(routes=routes, middleware=middleware)

if __name__ == "__main__":

As you can see, the GET /courses endpoint will just return a hardcoded list of courses.

We can fire the API up in a terminal using $ python, and leave it running.

Integrating the API with the CourseService

As a last integration step, we need to update the URL which the CourseService uses to fetch the courses:

// core/course.service.ts
// ...

  providedIn: "root",
export class CourseService {
  private apiUrl = "http://localhost:8000/courses";

  // ...

Fetching courses with the CourseService

We're now ready to plug the CourseService into the CourseListComponent!

Here are the steps we'll take to do it:

  1. Import the service.
  2. Inject it in the component using Angular's dependency injection.
  3. In the component's ngOnInit() method, get the RxJS observable to the list of course and subscribe to it.
  4. Store the fetched list of course on the component so that it gets rendered in the template.

Wondering how that translates into code? Take a look below β€” I added landmarks for each of the steps above:

import { Component, OnInit } from "@angular/core";
import { Course } from "../core/course.model";
// (1) Import
import { CourseService } from "../core/course.service";

  selector: "app-course-list",
  templateUrl: "./course-list.component.html",
  styleUrls: ["./course-list.component.css"],
export class CourseListComponent implements OnInit {
  courses: Course[];

  // (2) Inject
  constructor(private courseService: CourseService) { = [];

  ngOnInit() {
    // (3) Subscribe
    this.courseService.list().subscribe((courses: Course[]) => {
      // (4) Store = courses;


There you go! If we open the browser at http://localhost:8000, we see the list of courses displayed in sexy Times New Roman.

Styling is, indeed, out of the scope of this blog post.
Styling is, indeed, out of the scope of this blog post.

Wrapping up

Alright, let's see what we've achieved here:

  1. We generated the CourseListComponent using Angular CLI.
  2. We set up the component's courses attribute and its [template].
  3. We used Python and Starlette to build the API endpoint to test our component against.
  4. We used the CourseService and RxJS to fetch the list of course.

In fact, this is quite a typical workflow for me when I build web apps using Angular β€” I start by stubbing out the components, then implement the backend endpoints I need, and integrate them with the services to finally display the data.

If you're interested in the code, I uploaded it to a GitHub repo: ng-courses.