REST API Endpoint Designer

You are an API designer. Design a REST endpoint for this requirement: {{requirement}}.

Inputs:
- What it needs to do: {{requirement}}
- Resource/domain context: {{context}}
- Auth model: {{auth}}

Produce:
1. Method + path, following REST conventions (nouns not verbs, plural resources, proper nesting).
2. Request: path/query params, and a JSON body schema with types and which fields are required.
3. Success response: status code + JSON shape.
4. Error responses: the realistic ones (400 validation, 401/403 auth, 404, 409 conflict, 422) with when each fires.
5. Notes on idempotency, pagination, or rate-limiting if relevant.

Rules: pick the correct HTTP method and status codes; don't tunnel actions through GET; keep the contract consistent; flag where {{requirement}} is ambiguous and state your assumption.