Intermediate
APIs and REST for Network Engineers
The HTTP request/response model, the requests library, JSON responses, and safe read-before-write API automation — the same VLAN health-check lineage since Phase 2.6, now over HTTP instead of SSH.
Not every modern platform speaks SSH -- controllers and cloud-managed systems increasingly speak HTTP instead, and this module is your introduction to that world. You'll learn the client/server request-response model, install and use the requests library to make a safe, read-only GET request, and parse a JSON response into the same dict and list shapes you already know from earlier modules. From there you'll cover REST's resource-oriented URL design, handling 4xx/5xx errors and timeouts as expected outcomes rather than afterthoughts, and token-based authentication for the rare case where a mutating call is actually justified.
Next up
What Is an API? HTTP for Network Engineers
0 / 7 completeLessons
- 1
What Is an API? HTTP for Network Engineers
The client/server HTTP request-response model, positioned directly against the CLI/SSH model this curriculum has used since Netmiko Fundamentals — and why controllers and cloud-managed platforms increasingly speak HTTP instead of (or alongside) SSH.
Intermediate11 min readNext up - 2
Making a Safe GET Request
Installing requests, and making a real, read-only GET request against a local mock API — the same read-first discipline this curriculum has used since Netmiko Fundamentals, now applied to HTTP.
Intermediate12 min read - 3
Reading Structured JSON Responses
Parsing response.json() into the exact dict/list shapes already familiar from every prior module — an API response is structured data from the moment it arrives, unlike raw CLI text.
Intermediate11 min read - 4
Endpoints, Resources, and Parameters
REST's resource-oriented URL design — path parameters that pick out which device, and query parameters that filter what's returned — verified directly against this module's mock API.
Intermediate11 min read - 5
Handling Errors, Timeouts, and Status Codes
4xx/5xx status codes, raise_for_status(), and real timeout/connection-error handling — treating failure as an expected, first-class case, not an afterthought, verified directly against every failure mode this module's mock API can produce.
Intermediate14 min read - 6
Authentication and the Read/Write Safety Boundary
Token-based authentication headers, POST/PUT/PATCH/DELETE, and why a mutating API call deserves exactly the same caution send_config_set() and ios_config already taught — verified against a safe local mock, never a real controller.
Intermediate13 min read - 7
Capstone: An API-Driven Network Health Check
The complete pipeline: inventory, a GET request per device, JSON parsing, validation against required state, classification, and a JSON report — the same lineage as every capstone since Phase 2.6, now via HTTP instead of SSH.
Intermediate18 min read
Practice this module
Apply what you just covered -- hands-on practice and a knowledge check for this module.