frappe-errors-api

What problem does it solve?

Frappe/ERPNext REST endpoints can misbehave when errors are not clearly defined or communicated, leading to silent failures and poor client handling.

Core Features & Use Cases

• Provides a standardized mapping of common HTTP status codes to Frappe exceptions (400/417 for validation, 403 for permission, 404 for not found, 500+ for server errors).
• Enforces explicit input validation, permission checks, consistent error responses, logging, and retry/backoff patterns for 5xx responses.
• Useful for building robust API modules, webhooks, and external integrations with predictable error handling and audit trails.

Quick Start

Setup a whitelisted API endpoint to raise specific exceptions, log errors, and return structured error payloads to clients.