Integration training for the people who specify it
Practical sessions on APIs, integration and systems analysis, written for the analyst's side of the work. Free, self-paced, with a live demo API you can call from any browser.
Available now
API Integration for Analysts
Four sessions on the analyst's side of integration work: choosing between styles, writing requirements a developer can build from, specifying security, and keeping an API documented and testable. Built around a live demo API you can call yourself.
- 01 How systems really talk to each other The API and integration landscape — a working map for analysts
- 02 Before build starts API requirements and integration design — the analyst's half of the work
-
03 API security
-
04 Documentation, testing and lifecycle
What this is
There is plenty of good API material around, and most of it is aimed at the people who will implement the thing. Analysts have an adjacent job: helping decide whether an integration is needed, what it must do, what happens when it fails, and who should be in the room before design starts.
CyberNotes publishes training for that side of the work. Each session is a complete 90-minute deck you can work through at your own pace, with a PDF fallback and hands-on material that runs against a live API.
I built these for analysts I work with. They worked well enough in a room that keeping them private stopped making sense.
How it is put together
A live API, not screenshots. The hands-on sections run against a working demo API — a fully synthetic motor-insurance register built for this series. Credentials take seconds, with no account, no email address, and no corporate laptop required.
Examples from real systems. Vehicle registries, insurance bureaus, cross-border data exchange in the Baltic region — the ones this audience actually meets.
Aimed at the analyst’s half. Requirements, error paths, trade-offs, and who to involve, rather than implementation.
Including when not to build one. Deciding an integration is not needed is often the cheapest decision available, and it is easy to skip past.
Honest about its limits. Each session says where it stops and points at the reference material I would use myself.
Free, and reusable
Everything here is published under Creative Commons BY-SA 4.0. Use it, adapt it, teach from it — attribution and share-alike is all I ask.