Reviewed implementation notes
Developer guides for decisions that cross API boundaries
Endpoint reference tells you what one route accepts. These guides answer the next question: which routes belong in a real workflow, what evidence to keep, and where the boundary of the answer actually is. There are exactly three reviewed guides; this is a small editorial layer, not a generated page farm.
Choose by task
Three distinct workflows
01 · Testing workflow
Build deterministic test fixtures you can replay
A practical workflow for repeatable API fixtures: pin the seed, every shape parameter and any date window or as-of anchor, then save the resolved contract.
Task: Create a fixture that stays useful across local runs and CI without freezing accidental defaults into the test.
02 · Scheduling workflow
Build holiday-aware schedules without guessing dates
Choose the right holiday, business-day and timezone operation; audit every skipped date; and handle partial national calendars without overstating coverage.
Task: Calculate a deadline or available work window around national holidays, then preserve enough evidence to explain the result.
03 · Protocol workflow
Use the HTTP and URL APIs as a debugging toolkit
A standards-grounded workflow for canonical URLs, method and status references, Accept negotiation, registered fields and browser CORS diagnostics.
Task: Turn a pasted URL and an HTTP exchange into a reproducible diagnostic without claiming to contact, secure or validate the remote service.