Exceptions

Raise one of these anywhere and Feather turns it into the correct HTTP response, with no error handling in your routes.

from feather.exceptions import (
    ValidationError,        # 400, invalid input
    AuthenticationError,    # 401, not logged in
    AuthorizationError,     # 403, no permission
    AccountPendingError,    # 403, account awaiting approval
    AccountSuspendedError,  # 403, account suspended
    NotFoundError,          # 404, resource not found
    ConflictError,          # 409, already exists
)

What a client sees

raise ValidationError('Email is required', field='email')

{
  "success": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Email is required"
  }
}

API routes (/api/...), htmx requests and requests that ask for JSON get that body. A page gets a page: AuthenticationError sends the visitor to sign in, the account status errors below redirect, and a NotFoundError raised under a page route renders the 404 page for a browser (a request that accepts HTML) (templates/errors/error.html), so a service can raise it for a record that is gone, or belongs to someone else, and the browser shows a proper “not found”.

Account status exceptions

AccountPendingError and AccountSuspendedError inherit from AuthorizationError, but redirect to dedicated status pages instead of returning a generic 403.

Exception	Redirects to
`AccountPendingError`	`/account/pending`
`AccountSuspendedError`	`/account/suspended`

@auth_required raises them for you based on the user’s active and approved_at fields, so you never raise them directly. Both pages are scaffolded into your app. Edit them in templates/pages/account/ to match your branding.

Get started

Tutorial: build a Kanban app

Building the UI

Backend

Features

Tooling

Testing

Deployment

What a client sees

Account status exceptions

​What a client sees

​Account status exceptions

What a client sees

Account status exceptions