API errors & retries
Cover security and operational gates
Least privilege, negative probes, and a timed rollback beat a security essay about resilient TypeScript fetch wrapper around POST /v1/chat.
1Learn the idea
Read
Least privilege for this lab
Separate runtime and operator roles for resilient TypeScript fetch wrapper around POST /v1/chat. Runtime may only perform the narrow actions that mobile client waiting on a grounded answer needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to 429 storm with missing Retry-After that would amplify to 40 calls.
Read
Data and secret hygiene
Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident INC-429-2026-07-11 should be impossible if these controls hold. Output allowlists and schema checks stay in force on error paths.
Read
Implementation artifact
if (init.method !== "GET" && !headers.has("Idempotency-Key")) {
throw new SafeError("missing_idempotency_key"); // block blind replay of paid completions
}
redact(headers, ["authorization", "cookie"]);
Read
Rollback drill
Rehearse the rollback or kill switch timed against a clock. Record actor, reason, prior revision/secret/flag, and verification query. Invariant reminder: attempts ≤ 3, wall budget ≤ 8s, non-idempotent POSTs never replay without Idempotency-Key.
Read
Stage depth
Abuse cases unique to this lab include the privilege path implied by 429 storm with missing Retry-After that would amplify to 40 calls. Prove a read-only role cannot mutate. Break-glass tokens expire; leftover tokens fail the drill. Dependency pin/digest story matters when images or models move under you. Document how to rotate the credential that resilient TypeScript fetch wrapper around POST /v1/chat uses without a full outage window longer than your dual-run plan. Security evidence is part of ship, not an appendix nobody reads.
Read
Field notes for `api-error-handling` / `security-ops`
List network egress destinations and justify each. Ensure debug endpoints are off by default in the shipping config. Verify that error responses do not echo secrets or raw stack frames to clients. For multi-tenant paths, add a cross-tenant probe fixture. Time the rollback drill twice — once with the author, once with a peer. Store the drill transcript beside the threat notes for the incident id. In this chapter the product is resilient TypeScript fetch wrapper around POST /v1/chat, the human stakeholder is mobile client waiting on a grounded answer, and the incident id you design against is INC-429-2026-07-11. Re-state the oracle in your notes — 429 + Retry-After:2 → sleep once → 200 with attempts=2 — and keep the invariant visible: attempts ≤ 3, wall budget ≤ 8s, non-idempotent POSTs never replay without Idempotency-Key. Track retry_attempts_total{outcome} and p95 wall_ms ≤ 8000 as the scoreboard. Surface under change control: POST /v1/chat. If you only have forty minutes, finish the fixture for 429 storm with missing Retry-After that would amplify to 40 calls before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.
Go deeper
Before you start
Why this matters
Threat-model resilient TypeScript fetch wrapper around POST /v1/chat in five minutes: who can change config, who can read secrets, what a malicious payload tries to do. Write one negative probe that must yield deny with zero side effects. Reference INC-429-2026-07-11 as the story you refuse to repeat.
In the wild
See how this idea shows up as a product and a company — then come back to the lesson. Skills transfer across vendors.
Related lessons
Check your understanding
Page assessment
Answer from memory. Completion is saved from this evidence, not from opening the next page.
All responses are required.