We.ProtectAcademy

Learn to protect what matters

03

Guided lesson

How APIs Connect Applications

Understand how two applications exchange information through a structured request and response.

Not Started 7 min Beginner
Step 1 of 714% contentKnowledge check pending

Objectives

By the end of this lesson, you will understand:

  • Understand how one application asks another for data.
  • Recognise an endpoint, a method and a request.
  • Explain what a response and a status code tell you.
  • Describe why a shared data format helps.

Concept flow

Application asks

Stage 1 of 4

One app sends a structured request for data or an action.

Possible defensive checkpoints

AuthenticationInput validationRate limits

The app sends a request

One application asks for something specific.

What you are seeing
  1. A retailer app icon appears
  2. A request bubble forms with a short message
  3. The bubble moves toward the API

Simple explanation

A request is a structured question. It says which application is asking and what it wants.

At Brightline Parts, a retailer asks for the stock level of a brake pad.

Why this matters

A clear question gets a clear answer.

Key termRequest

Knowledge check

Show what you learned

Answer every question. You do not need a perfect score to complete the lesson.

3 questions
  1. 01In the restaurant analogy, what is the API like?
  2. 02A status code of 200 means the request worked.
  3. 03Brightline Parts returns a stock number in a block with named values like 'part' and 'count'. What format is this most likely?

SIMULATION

Match the API Parts

Cedarline Studio's shop asks a warehouse app for stock counts through an API.

Match each API part to what it means.

SIMULATION · weprotect-demo-tenant · FIXTURES · Demo tenant · isolated fixtures · no customer data

Score: 0% · Best: 0%

Stage 1 of 4
UserPersonDeviceEndpointIdPIdentityGatewayPolicyWebFront doorAPIInterfaceSIEMDetectionDataStore
REQUESTWhat is a 'request' in this exchange?

Live metrics

USERS1240
AUTHENTICATIONS / MIN86
FAILED LOGINS4
ALERTS2
CRITICAL FINDINGS0
RISK SCORE22 / 100
OPEN INCIDENTS0
SLA TIME45 min
ENDPOINT HEALTH98%
ASSETS AT RISK0
verificationStatusPending
productionImpactNone

Scenario parameters

Asset
IDENTITY-CORE
Exposure
internet
Production criticality
medium
EDR health
96
Approval required
No
Maintenance window
02:00–03:00 UTC (planned)

Simulation paused at a decision point

What is a 'request' in this exchange?

Ready to read
SIMULATION

Using a system fallback voice; quality may vary.

Read instead

Captions: Welcome to this simulation: Match the API Parts. This is an isolated training environment with demo fixtures.

Assessment

Formal lesson assessment

5 questions. A score of 70% or higher demonstrates mastery. Answers stay hidden until you submit.

0/5 answered
  1. 01A status code of 200 means the request worked.

    Difficulty 2 · true false

  2. 02What is the main job of an API in a web application?

    Difficulty 2 · multiple choice

  3. 03Wingtip Toys has an API that returns customer orders. It slows down when many callers ask at once, and a few callers retry very aggressively. Which control most directly protects the API's availability?

    Difficulty 3 · multiple choice

  4. 04Brightline Parts returns a stock number in a block with named values like 'part' and 'count'. What format is this most likely?

    Difficulty 4 · scenario

  5. 05In the restaurant analogy, what is the API like?

    Difficulty 2 · multiple choice

Answer every question before submitting.

AI tutor

Help only. The tutor never changes scores, progress records, or certificates.

What makes this lesson complete

  • Lesson content: pending
  • Simulation: pending
  • Assessment: pending