Do not use separate API endpoints for working on a single record and on multiple records
Up till now, when designing/coding API endpoints for resources, I would have separate API endpoints for working on a single record and on multiple records, e.g. /api/actor/123/edit (with record ID set as path parameter) and /api/actor/edit (with record IDs set in POST request body) for the “actor” resource. This would inevitably result in duplication of …