← Prompt Library / Engineering
Write API error responses developers thank you for: precise codes, actionable messages, and the docs link that fits the error.
Write error responses for my API: {{endpoints_errors}} (the endpoints and the failure cases). Per error: the right HTTP status (and the reasoning where it's debatable), a machine-readable error code (stable, greppable), the human message that says what happened AND what to do ('rate limit exceeded: retry after 30s' — include the values), the field-level detail for validation errors (which field, what rule), and the docs anchor per error class. Consistency check: same shape everywhere, no HTML in JSON errors, no stack traces in production. Include the error-response envelope spec.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...